intent-review
Interactive approval system for reviewing architecture intent sections.
Install
mkdir -p .claude/skills/intent-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16231" && unzip -o skill.zip -d .claude/skills/intent-review && rm skill.zipInstalls to .claude/skills/intent-review
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Interactive Intent approval. Review sections and mark status (locked/reviewed/draft). Use /intent-review <path> to review a specific file, or /intent-review to review Intent in current directory.Key capabilities
- →Parse Intent files to identify sections
- →Display an overview of section statuses (LOCKED, REVIEWED, DRAFT)
- →Interactively ask for approval on unmarked sections
- →Update markdown files with status tags
- →Detect modifications to LOCKED sections
- →View approval history for sections
How it works
The skill parses an Intent file, identifies sections, displays their current status, and then interactively prompts the user to mark unmarked sections as LOCKED, REVIEWED, or DRAFT, updating the file accordingly.
Inputs & outputs
When to use intent-review
- →Reviewing architectural design docs
- →Marking sections for approval
- →Updating intent status
About this skill
Intent Review
交互式 Section 级别的 Intent 审批工具。
核心概念
Intent 文档按 Section 粒度审批,三种状态:
| 状态 | 标记 | 含义 | Agent 行为 |
|---|---|---|---|
| LOCKED | ::: locked | 核心架构,修改需 human 明确同意 | 暂停,请求确认 |
| REVIEWED | ::: reviewed | 已审阅,可修改但需通知 | 允许,事后通知 |
| DRAFT | ::: draft | 草稿,可自由迭代 | 自由修改 |
工作流程
/intent-review [path]
↓
┌───────────────────┐
│ 解析 Intent 文件 │
│ 识别所有 Section │
└─────────┬─────────┘
↓
┌───────────────────┐
│ 展示状态概览 │
│ N locked │
│ M reviewed │
│ K draft/unmarked │
└─────────┬─────────┘
↓
┌───────────────────────────────────────┐
│ 逐个未标记 Section 询问 │
│ │
│ AskUserQuestion: │
│ "Section: [标题]" │
│ 选项: │
│ - Lock (核心架构) │
│ - Review (确认接受) │
│ - Skip (保持 draft) │
└─────────┬─────────────────────────────┘
↓
┌───────────────────┐
│ 更新文件 │
│ 添加标记和属性 │
└───────────────────┘
使用方法
审批指定文件
/intent-review src/core/intent/INTENT.md
审批当前模块
cd src/chambers/terminal
/intent-review
自动查找 intent/INTENT.md
批量审批
/intent-review --all
扫描项目所有 intent 文件
执行步骤
1. 定位 Intent 文件
// 优先级:
// 1. 用户指定路径
// 2. 当前目录下 intent/INTENT.md
// 3. 当前目录下 INTENT.md
2. 解析 Section
识别两种 Section:
已标记的:
::: locked
## 模块边界
...
:::
未标记的(普通 markdown heading):
## API 设计
...
3. 展示概览
Intent Review: src/core/intent/INTENT.md
状态概览:
├── 🔒 LOCKED: 2 sections
│ ├── 模块边界规则
│ └── 数据结构
├── ✓ REVIEWED: 3 sections
│ ├── API 签名 (by robert, 2026-01-19)
│ ├── 配置格式
│ └── 错误处理
└── 📝 UNMARKED: 4 sections
├── 实现建议
├── 性能考虑
├── 示例代码
└── 变更记录
是否开始审批未标记的 sections?
4. 逐个审批
对每个未标记 Section 使用 AskUserQuestion:
使用 AskUserQuestion:
- question: "Section: API 签名\n\n内容预览:定义了 create(), delete(), list() 三个函数..."
- header: "审批状态"
- options:
- label: "Lock (核心架构)"
description: "锁定此 section,修改需要 human 明确同意"
- label: "Review (确认接受)"
description: "标记为已审阅,Agent 可修改但需通知"
- label: "Skip (保持 draft)"
description: "暂不审批,保持草稿状态"
5. 更新文件
根据用户选择,在 markdown 中添加标记:
Lock 选择:
::: locked {reason="核心架构"}
## API 签名
...
:::
Review 选择:
::: reviewed {by=<username> date=<today>}
## API 签名
...
:::
Skip 选择: 不修改,或添加:
::: draft
## 实现建议
...
:::
特殊场景
检测 LOCKED Section 被修改
当文件有未提交的修改时:
⚠️ 检测到 LOCKED section 被修改:
- Section: 模块边界规则
- 修改内容: [diff preview]
此修改需要 human 明确同意。是否接受?
查看审批历史
/intent-review --history src/core/intent/INTENT.md
输出:
Section: API 签名
├── 2026-01-19 robert: reviewed
├── 2026-01-15 robert: draft → reviewed
└── 2026-01-10 created
Section: 模块边界
├── 2026-01-18 robert: locked (reason: 核心架构)
└── 2026-01-12 created
与其他工具配合
intent-interview → 创建 Intent (默认全是 draft)
↓
/intent-review → 审批关键 sections
↓
aine-dev-flow → 开发实现 (遵守 locked/reviewed 规则)
↓
intent-sync → 检查一致性
配置
可在 ~/.claude/settings.json 中配置默认 reviewer:
{
"idd": {
"reviewer": "robert",
"autoLockPatterns": ["模块边界", "数据结构", "安全约束"]
}
}
When not to use it
- →When the user does not want interactive approval
- →When the intent file is not in markdown format
- →When the user does not want to update the file with status tags
Limitations
- →Requires markdown files for Intent documentation.
- →Relies on user interaction for marking section statuses.
- →Detects modifications to LOCKED sections but requires human confirmation for acceptance.
How it compares
This skill provides an interactive workflow for section-level approval and status tagging within Intent files, which is more structured and auditable than manual review processes.
Compared to similar skills
intent-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| intent-review (this skill) | 0 | 6mo | No flags | Beginner |
| specification-architect | 13 | 9mo | Review | Advanced |
| business-analyst-authority | 0 | 4mo | No flags | Advanced |
| adr | 0 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
specification-architect
adrianpuiu
A rigorous, traceability-first system that generates five interconnected architectural documents (blueprint.md, requirements.md, design.md, tasks.md, and validation.md) with complete requirements-to-implementation traceability. Use this skill when users need to architect systems, create technical specifications, or develop structured project documentation with guaranteed traceability.
business-analyst-authority
ahmedemad3
Act as a Principal Business Analyst (8+ years exp) bridging the gap between Strategy and Execution. Specializes in translating vague vision into rigorous technical specifications using Gherkin (BDD), BPMN 2.0, and strict Requirement Engineering standards.
adr
rvdbreemen
Architecture Decision Record (ADR) management skill. Creates, maintains, and enforces architectural decisions. Ensures code changes align with documented decisions. Documents alternatives considered and rejected. Facilitates architectural planning and human decision documentation.
specification-refiner
ddunnock
>
okf-adr-review
lilabrooks
Accept or reject a proposed ADR at the owner's direction — status flip, reversal per rollback trigger, index and log updates. Use when the owner reviews pending decisions, says to accept/reject an ADR, or asks what's awaiting review.
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.