القائمة
Use after an approved spec to create a dependency-ordered software delivery plan and tasks.yaml skeleton before task contracts or implementation.
التثبيت باستخدام 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 implementation to run a full generic code review, validate findings, and write a prioritized implementation plan for confirmed fixes.
Use when turning a raw software feature idea into an approved specification before planning, tasks, implementation, review, or finalization.
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-plan |
| description | Use after an approved spec to create a dependency-ordered software delivery plan and tasks.yaml skeleton before task contracts or implementation. |
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.
spec.md and target repo context.plan.md and a tasks.yaml skeleton.# <Feature> Plan
## What This Delivers
## Task DAG
| # | Task | Areas touched | Depends on |
|---|---|---|---|
## Cross-Task Decisions
## Global Verification Gates
## Boundaries
tasks.yaml SkeletonUse .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.
plan.md + tasks.yaml skeleton -> pipeline-tasks.