| name | pipeline-plan |
| description | Use after an approved spec to create a dependency-ordered software delivery plan and tasks.yaml skeleton before task contracts or implementation. |
Pipeline Plan
Stage 2: spec -> plan.
Turn .pipeline/<feature>/spec.md into .pipeline/<feature>/plan.md and a
tasks.yaml skeleton. The plan sequences work; it does not pre-render code.
Process
- Read
spec.md and target repo context.
- Slice the feature into small, independently verifiable tasks.
- Order tasks by dependency and identify parallel branches.
- Carry forward cross-task decisions from the spec.
- Write
plan.md and a tasks.yaml skeleton.
Plan Shape
# <Feature> Plan
## What This Delivers
## Task DAG
| # | Task | Areas touched | Depends on |
|---|---|---|---|
## Cross-Task Decisions
## Global Verification Gates
## Boundaries
tasks.yaml Skeleton
Use .agents/pipeline/schemas/tasks.schema.json. Set each task status to
pending. Fill areas from the plan and leave anchors/verify for
pipeline-tasks if not known yet.
Handoff
plan.md + tasks.yaml skeleton -> pipeline-tasks.
