메뉴
Use after a delivery plan exists to write thin per-task implementation contracts and complete tasks.yaml for execution.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | pipeline-tasks |
| description | Use after a delivery plan exists to write thin per-task implementation contracts and complete tasks.yaml for execution. |
Stage 3: plan -> executable tasks.
Turn a plan DAG into one thin task contract per node:
.pipeline/<feature>/tasks/NN-<slug>.md.
spec.md, plan.md, and the target repo context.tasks.yaml so every node has areas, anchors, verify, and
status: pending.# Task NN: <Title>
## Goal
## Inputs
- Spec:
- Plan:
## Anchors And Invariants
- <symbol/file/command/contract> MUST ...
## Expected Changes
## Verify
- <command>
## Acceptance
- <observable result>
tasks.yaml + tasks/ -> pipeline-implement.
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 when turning a raw software feature idea into an approved specification before planning, tasks, implementation, review, or finalization.
Use after pipeline-review-and-plan reviewer reports exist to eliminate false positives and write a prioritized implementation plan from confirmed findings.