القائمة
Use after tasks.yaml and thin task contracts exist to implement the dependency-ordered task graph and mark tasks done only after verification passes.
التثبيت باستخدام 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 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 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-implement |
| description | Use after tasks.yaml and thin task contracts exist to implement the dependency-ordered task graph and mark tasks done only after verification passes. |
Stage 4: tasks -> implementation.
Execute .pipeline/<feature>/tasks.yaml. Work in dependency order. Use
parallel agents only when the active tool supports them and the tasks are truly
independent; otherwise run sequentially.
tasks.yaml and all pending task contracts.done.verify commands.done only if verification passes.blocked when the task contract is wrong, underspecified, or
cannot be made green without changing decisions from spec.md or plan.md.done, run final_gate from tasks.yaml.Assembled implementation with green task gates -> pipeline-review-and-plan.