Reviewing
If preflight readiness is missing, stale, or blocked (check .pulse/tooling-status.json), stop and invoke pulse:using-pulse before continuing.
br is required for reviewing. If br is unavailable, Gate 4 cannot run; stop immediately and route to preflight/tooling remediation via pulse:using-pulse.
Reviewing is the last automated quality gate before shipping. It verifies behavior, safety, and completeness for Pulse ecosystem closeout rather than trusting bead closure alone.
When to Invoke
- After
pulse:swarmingreports final current work is complete and the approved shape artifacts plus.pulse/STATE.mdagree no later work remains (work-shape.md,phase-plan.md, orepic-map.md+current-story-pack.mdwhen epic-map is active) - During Pulse ecosystem closeout immediately before Gate 4 decisioning
- Optional flags:
--serial,--skip-uat(only when human UAT is intentionally omitted and non-interactive evidence is used)
Required Inputs
Read before starting:
.pulse/project-docs.jsonwhen present, plus minimal relevant listed docshistory/<feature>/CONTEXT.mdhistory/<feature>/approach.mdhistory/<feature>/lifecycle-summary.mdwhen present.pulse/STATE.md- reviewing-owned changeset evidence for the active Pulse closeout path
If .pulse/project-docs.json is absent, detect and read the smallest relevant project docs (README, architecture, ADR, domain docs).
Runtime Contract
All execution-time rules live in references/runtime-appendix.md. Treat that file as canonical for:
- 4+1 review orchestration
- severity mapping and review bead creation rules
- Gate 4 hard-block behavior for P1
- artifact verification contract and severity mapping
- UAT failure routing
- finishing checklist and closeout
Minimum Flow
- Run specialist review (4+1 model).
- Run artifact verification for all promised deliverables.
- Turn every accepted finding into a review bead by severity and deduplicate overlaps before presenting results.
- Enforce hard gate: if any P1 review bead exists, stop and present the blocking bead IDs; do not continue closeout.
- Run human UAT unless explicitly skipped under allowed mode.
- If UAT or finishing checks reveal new accepted findings, create or update the corresponding review/fix beads before proceeding.
- Execute finishing and update Pulse state artifacts.
- Recommend
pulse:compoundingas the next skill and default tonext_action: manual_invoke.
Handoff
If paused, write a reviewing-owned handoff using ../using-pulse/references/handoff-contract.md and register it in .pulse/handoffs/manifest.json.
After finishing completes, report feature completion, update runtime state for Gate 4 approval, and recommend compounding without auto-triggering it unless the user explicitly asks to continue now.
References
references/runtime-appendix.md— canonical runtime contractreferences/review-agent-prompts.md— exact prompts for all 5 agentsreferences/review-bead-template.md— review bead format and creation contract