메뉴
Reviews a spec or structured document for implementability, control-flow soundness, and cross-reference consistency before execution begins. Uses a director-holds-context pattern with targeted subagent prompts that trace state through branches and verify interface agreement.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Articulates the why behind a candidate queue item — its direction, its named uncertainty, and the conscious scope-carve — and gates it through a cold-context review before writing the QUEUE.md row that the gate lifecycle binds to.
Authors a gate document for a queue item — a production validation plan that defines what must be proven before work is considered done. Applies the quality bar and self-assessment questions that gate-review audits against.
Loads and summarizes session context by reading the doctrine, project index, queue, and triage state.
Runs a structured retrospective of a completed work session — captures what specs, gates, and plans miss. What actually happened, where friction occurred, and what to change next time. Domain-agnostic methodology.
Audits an existing gate document against the gate-plan quality bar — the quality assurance step between plan and work. Produces findings (structural compliance, quality findings, self-assessment gaps, strengths) and a PASS/FAIL verdict with confidence rating.
Executes an operator-authored gate document by loading it into context and working through each checkpoint as the executing agent — no subagent dispatch. Handles resume of partially-completed gates against the operator's validation plan.
| name | spec-review |
| description | Reviews a spec or structured document for implementability, control-flow soundness, and cross-reference consistency before execution begins. Uses a director-holds-context pattern with targeted subagent prompts that trace state through branches and verify interface agreement. |
| when_to_use | Use when the user asks to review/validate/critique a spec, check whether a spec is implementable, find problems in a spec or design doc, or wants a structured review of a plan before implementation. |
The reviewer's director holds the context, writes the subagent prompt, and triages the results.
When constructing the subagent prompt, include:
Round 1 is a broad sweep. Expect 5-15 findings across severity levels.
Subsequent rounds are targeted. Exclude prior findings and focus on areas not yet covered.
Two to three rounds is typically sufficient. After each round, report the severity level of findings and whether another round is likely to surface actionable issues.
Stop after findings drop to minor severity unless the user explicitly requests another round.
