メニュー
Use when turning a raw software feature idea into an approved specification before planning, tasks, implementation, review, or finalization.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use after review-and-plan to verify the full pipeline ran, implementation aligns with the spec, final gates pass, and human plus agent journey coverage exists.
Use after tasks.yaml and thin task contracts exist to implement the dependency-ordered task graph and mark tasks done only after verification passes.
Use after an approved spec to create a dependency-ordered software delivery plan and tasks.yaml skeleton before task contracts or implementation.
Use after implementation to run a full generic code review, validate findings, and write a prioritized implementation plan for confirmed fixes.
Use after a delivery plan exists to write thin per-task implementation contracts and complete tasks.yaml for execution.
Use after pipeline-review-and-plan reviewer reports exist to eliminate false positives and write a prioritized implementation plan from confirmed findings.
| name | pipeline-spec |
| description | Use when turning a raw software feature idea into an approved specification before planning, tasks, implementation, review, or finalization. |
Stage 1: idea -> spec.
Create .pipeline/<feature>/spec.md. The spec is the decision authority for
the rest of the pipeline. Do not write code or a commit/task plan in this stage.
pipeline-plan.# Spec: <Feature>
## Objective
## Success Criteria
- Include observable user outcomes.
- Include expected human and agent/headless journeys.
## Users And Agent Surfaces
## Scope
- In:
- Out:
## Contracts And Interfaces
- APIs, CLIs, SDKs, schemas, UI routes, config, docs, generated artifacts, or
tool contracts that change.
## Decisions
- Decision:
- Why:
- Consequences:
## Test Journeys
- Human journey:
- Agent/headless journey:
## Open Questions
.pipeline/<feature>/spec.md -> pipeline-plan.