メニュー
Use after execution completes when the user needs final quality verification and release-readiness review before closeout.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | reviewing |
| description | Use after execution completes when the user needs final quality verification and release-readiness review before closeout. |
| metadata | {"version":"1.3","ecosystem":"pulse","upstream":"swarming","downstream":"compounding","dependencies":[{"id":"beads-cli","kind":"command","command":"br","missing_effect":"unavailable","reason":"Reviewing creates review beads and closes the epic through br."},{"id":"beads-viewer","kind":"command","command":"bv","missing_effect":"unavailable","reason":"Reviewing verifies the live bead graph before epic closeout."}]} |
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.
pulse:swarming reports final current work is complete and the approved shape artifacts plus .pulse/STATE.md agree no later work remains (work-shape.md, phase-plan.md, or epic-map.md + current-story-pack.md when epic-map is active)--serial, --skip-uat (only when human UAT is intentionally omitted and non-interactive evidence is used)Read before starting:
.pulse/project-docs.json when present, plus minimal relevant listed docshistory/<feature>/CONTEXT.mdhistory/<feature>/approach.mdhistory/<feature>/lifecycle-summary.md when present.pulse/STATE.mdIf .pulse/project-docs.json is absent, detect and read the smallest relevant project docs (README, architecture, ADR, domain docs).
All execution-time rules live in references/runtime-appendix.md. Treat that file as canonical for:
pulse:compounding as the next skill and default to next_action: manual_invoke.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/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 contractUse after completed Pulse work when the user asks to capture post-cycle machine-readable learnings for future planning and execution.
Use when the user asks to distill accumulated dev-notes into reader-facing topic knowledge, rather than to capture a new note or update machine memory.
Use when implementing approved Pulse beads, either as a swarm worker or as a single worker when swarming is unavailable.
Use before implementation planning when feature intent is clear but implementation decisions are still unresolved, and the user needs those decisions locked first.
Use after pulse:exploring when locked decisions are ready and the user needs a mode-gated plan with an approved work shape and current-work prep for validation.
Use when starting any Pulse workflow, resuming a Pulse session, or before planning or execution when tool readiness or onboarding state may block the flow.