review-spec-plan
Reviews a spec or plan in four gated stages (need or root cause, solution design, impact, spec quality) with one reviewer seat per pass, stopping at the first failing stage; a passed stage is frozen. Use when a spec or plan should be reviewed before it is built or its issues are resolved.
- License 许可
- MIT
- 最近更新
- 2026-11-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- review-spec-plan
- effort
- high
- description
- Reviews a spec or plan in four gated stages (need or root cause, solution design, impact, spec quality) with one reviewer seat per pass, stopping at the first failing stage; a passed stage is frozen. Use when a spec or plan should be reviewed before it is built or its issues are resolved.
- allowed-tools
- Agent, Bash, Read, Edit
- argument-hint
- [spec-or-plan-path] [base-sha]
- user-invocable
- true
- disable-model-invocation
- true
02 资源文件 4
- 参考文档references/lens-architect.md3.3 KB
- 参考文档references/lens-blast-radius.md2.9 KB
- 参考文档references/lens-root-cause.md3.7 KB
- 参考文档references/lens-spec-quality.md4.8 KB
03 SKILL.md 正文
Spec/Plan Review
Runs one review pass on the spec or plan at $0. The stages, lenses, round rules and Status line live in orchestrate's Spec review section, which this file reads and does not copy. Read-only on the target except its Status line.
Wallet: ${user_config.wallet} (unset, unknown or still literal text: sushi). The pass seat gets model from the spec review pass row and the wallet's column in the table printed by sed -n '/^## Route the seat/,/^## Brief/p' "${CLAUDE_PLUGIN_ROOT}/skills/orchestrate/SKILL.md".
- Target:
$0as an absolute path. Ask when it is missing; for a directory, list its.mdfiles and ask. A base$1makes this a re-review: the pass reads onlygit diff $1 -- <target>, and an empty diff is BLOCKED, never a full review. - Print
sed -n '/^## Spec review/,/^## /p' "${CLAUDE_PLUGIN_ROOT}/skills/orchestrate/SKILL.md"and follow it; in the printed text$+{CLAUDE_PLUGIN_ROOT}means ${CLAUDE_PLUGIN_ROOT}, so write resolved paths into the brief. The first unfrozen stage and the round come from this conversation (earlier passes,Stage <n> frozenorfixedlines), else from the target'sReview:Status clause, else stage 1, round 1. - Spawn one
senioro:investigatorwith a brief of MODEL, GOAL, READ, RULES, REPORT FILE and RETURN lines. READ names the target, the section'ssedcommand,${CLAUDE_PLUGIN_ROOT}/skills/orchestrate/references/stages.md, the stage, the round and the base. The report file is$HOME/.cache/senioro-tl/runs/${CLAUDE_SESSION_ID}/reports/spec-pass-<n>.md, written absolute (mkdir -pits directory). - Print the report's roster. A failing stage ends with
Next: /senioro:resolve-plan-issues <spec>. - When stage 4 passes, or the loop stops for the user, write the Status line once, as the section says.
04 同仓库更多 Skills
write-spec
Writes the technical spec for a framed goal or a product requirements document: decisions table, cited facts, root cause for fixes, design with alternatives, agreed test seams, and gateable units, then runs a hygiene pass. Use when a goal is framed and the technical how must be designed before building.
write-prd
Writes a product requirements document (problem, users, solution, user stories, success measure, out of scope) from a framed goal, recording only decisions the user made or confirmed. Use when a framed goal needs its product what and why settled before a technical spec.
unslop
Cuts AI tells from any writing, such as filler, hedging, AI vocabulary, em dashes, and jargon, while keeping the meaning and tone. Use when writing or editing prose such as docs, READMEs, PR descriptions, or commit messages, or when the technical-writing skill applies.
typescript-best-practices
Applies TypeScript best practices: discriminated unions, branded types, constructive modeling, no `as` casts, exhaustive switches, and validation at boundaries. Use when reading or editing any .ts or .tsx file.
technical-writing
Applies a layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
status
Prints a plain-language status digest of the current work: done (and how it was verified), in flight, left, next, and open decisions, from the session's progress or rebuilt from git and the spec. Use when the user asks where things stand or what is done, left, or next.