メニュー
Render the implementation handoff for a subject spec. Use this when the canonical readiness verdict already exists and you need either a real implementation plan for eligible runs or a withheld handoff plus bounded options for blocked runs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Stress-test a subject spec for ambiguity, gaps, contradictions, and untestable claims using dynamic agent teams. Use this when the spec has passed completeness and synthesis-review gates and needs adversarial validation before readiness promotion.
Stamp a self-replicating four-bead autoresearch loop (doer/judge/arbiter/strategist) for autonomous iterative improvement of any artifact. Use after interactive intake when you have a program and want to run an autonomous improvement loop with blind scoring. Triggers on: autoresearch, research loop, autonomous loop, overnight loop, iterative improvement.
Decompose an implementation plan into br beads with dependency wiring, epic grouping, and provenance labels. Use this after forge-plan-handoff when the user accepts the beads generation prompt.
Stress-test beads for coverage, granularity, dependency correctness, and actionability using adversarial agent teams. Use this after forge-beads-generate when the beads workspace is populated.
Score a subject spec against the ontology and canonical readiness contract. Use this when you need claim-level coverage scoring, corroboration checks, critical-decision coverage, risk-weighted assumptions, contradiction penalties, and blocker-aware 80/80 gates.
Normalize all starting evidence into a subject spec run. Use this when beginning a Forge spec from code, docs, transcripts, screenshots, URLs, or a sparse user request. Creates the subject slug, frontmatter, evidence ledgers, request archetype, evidence-density classification, and canonical readiness skeleton.
| name | forge-plan-handoff |
| description | Render the implementation handoff for a subject spec. Use this when the canonical readiness verdict already exists and you need either a real implementation plan for eligible runs or a withheld handoff plus bounded options for blocked runs. |
| allowed-tools | Read, Write, Glob, Grep |
Use this only after forge-orchestrator has finalized planning_status and
handoff_status.
Do not emit a real implementation plan if:
planning_status != PLANNING_READYhandoff_status != ELIGIBLEadversarial_status != convergedsparse analogy_feature or parity_clone with
question_rounds_completed = 0Read from canon and sidecars:
specs/<subject>.mddecision-log.mdcompleteness-matrix.mdreview-report.mdadversarial-review-log.mdUBIQUITOUS-LANGUAGE.md (project root, if it exists)AGENTS.md (project root, if it exists) — prior implementation conventions
that should inform workstream ordering, risk assessment, and anti-patterns
to avoidDo not plan directly from raw intake chatter.
If handoff_status=ELIGIBLE, create or update implementation-plan.md with:
If the run is blocked, write a withheld handoff note instead. Blocked handoff may include:
Blocked handoff must not include: