菜单
Review design specs for correctness, completeness, consistency, quality, implementability, and risks. Verifies claims against source code. Invoke with /review-spec <path-to-spec>.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
any input (code, docs, papers, images, videos) to knowledge graph. Use when user asks any question about a codebase, documents, or project content - especially if graphify-out/ exists, treat the question as a /graphify query.
Graphite CLI (gt) patterns for managing stacked pull requests. Use whenever the user mentions graphite, the `gt` command, PR stacks, or stacked diffs. Also triggers when starting development work in a repository where graphite is initialized (`.git/refs/graphite` exists or `gt` commands have been used). Invoke proactively when the user is creating branches, submitting PRs, or navigating between related branches in a collaborative repo — even if they don't mention graphite by name.
Use when creating issues, reviewing unestimated backlog items, or asked to estimate effort. Encodes the fibonacci scale and drives session/agent planning decisions.
Complete a development ticket end-to-end: root-cause any test failures, run the full test suite, lint and typecheck, commit, fast-forward merge to main, update the issue tracker to Done, and file follow-up issues for gaps. Invoke with /finish-ticket <ISSUE-ID>.
Session start check for MCP auth, git state, and worktree environment. Run at the start of any session involving MCP servers to surface expired tokens and env drift before they interrupt real work.
Technical documentation standards for both writing and reviewing. Use when creating new documentation, writing ADRs, drafting technical specs, reviewing existing docs for quality, or critiquing technical writing. Triggers on any documentation task, whether creating, editing, or reviewing.
| name | review-spec |
| description | Review design specs for correctness, completeness, consistency, quality, implementability, and risks. Verifies claims against source code. Invoke with /review-spec <path-to-spec>. |
Review implementation design specs by verifying claims against source code and evaluating across six dimensions.
Process:
Dimensions:
Output: Narrative findings by dimension, ending with a summary of substantive issues. Skip dimensions with nothing to report.
See reference.md for detailed standards.
