review

Review Orchestrator

Output Path — MANDATORY

All review output goes into a per-run, date-keyed folder under the feature's reviews/code/ directory:

{output_dir}/{feature}/reviews/code/{date}{_counter}/   ← {review_dir}
├── summary.md                       ← {review_summary}  (consolidated findings, main output)
├── changes.md                       ← applied-fixes log (side-artifact, written after step 9)
└── detailed/
    └── <agent>.md                   ← {review_detailed} (one per dispatched agent)

{output_dir}/{feature}/outputs/reviews/code/{date}{_counter}/  ← {review_outputs_dir}
├── summary.html                     ← {review_summary_html}
└── detailed/
    └── <agent>.html                 ← {review_detailed_html} (one per agent)

Where {output_dir} comes from .shield.json output_dir field (default docs/shield), {feature} is the feature folder name ({feature-name}-YYYYMMDD), {date} is today's ISO date (YYYY-MM-DD), and {_counter} is empty for the first run of the day or _2, _3, ... on same-day collisions. Numbered-run subfolders (code-review/{N}-{slug}/) are gone. Reviews never overwrite prior runs.

Resolving the counter: before writing, list {output_dir}/{feature}/reviews/code/ for entries matching today's date. If {date}/ does not exist, use _counter="". Otherwise, find the highest {date}_<N>/ and use _counter="_<N+1>". Do NOT use any other path or directory structure. The Write tool creates directories automatically.

When to Use

• After implementing a feature or story step
• When explicitly invoked via /review
• As the final review at the end of an implementation pipeline

When NOT to Use

• For plan review — use plan-review skill instead
• For a single specific reviewer — use /review-security, /review-cost, etc.

Step Skeleton

At startup, call execute-steps to register these steps. Execute them in order, updating status after each.

Step	Action	Condition	Mandatory
1	Load prior context (plan, research)	skip if none exists	No
2	Code correctness review	always	Yes
3	Domain-specific review	skip if no active domains	No
4	Dispatch agent reviewers	explicit/final review only	No
5	AC verification	skip if no plan.json	No
6	Merge + present findings	always	Yes
7	Apply selected fixes	always	Yes
8	Write summary + update manifest	always	Yes