ワンクリックで
implement-plan
phased implementation of a structured plan you must use this skill when asked to implement a plan file in .tasks/*
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
phased implementation of a structured plan you must use this skill when asked to implement a plan file in .tasks/*
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use only when the user explicitly asks or allows delegating implementation to a Codex worker — launch Pi running openai-codex/gpt-5.6-sol (xhigh) as a visible sidecar implementer that this session orchestrates over AMQ. Write exact task specs, dispatch with --kind todo, validate the results yourself, then iterate, resume, respawn, or launch another worker. Never invoke on your own initiative.
Use only when the user explicitly allows or asks for this skill to be invoked to pair with a second agent harness — launch a sidecar, get a second opinion from another agent, have one harness drive another, or review work with another agent over AMQ. Otherwise, never invoke it.
first step of planning
convert structure outline into a detailed implementation plan
Create a Product Requirements Document with inline mockups
generate research questions based on a task, spec, or ticket
| name | implement-plan |
| description | phased implementation of a structured plan you must use this skill when asked to implement a plan file in .tasks/* |
| disable_model_invocation | true |
| disable-model-invocation | true |
You are responsible for orchestrating the phased implementation of technical plans from .tasks/. You will work through each phase systematically using a specialized implementer agent.
For each phase in the implementation plan:
If you were provided with a path to a plan file, proceed with the plan.
If you were provided with a task artifact directory like .tasks/<task slug> you should list the contents with ls -La to locate the plan file inside of it, e.g. ls -La .tasks/<task slug>. Do NOT use Glob or Grep or ls without -L or with -l, as the directory may be a symlink.
Use the Task tool with subagent_type=implementer-agent to implement the current phase. Provide clear instructions about which phase to implement.
Example:
Implement Phase [N] of the plan at .tasks/ENG-XXXX-description/NN-plan-DESCRIPTION.md
Focus only on Phase [N] and stop after completing automated verification.
IMPORTANT - keep your prompt short, do not duplicate details that are already in the plan, because the implementer agent will read the plan.
Carefully review the implementer agent's output:
Run any automated verification that the implementer agent may have missed or that you can perform:
Provide a clear summary of the phase completion:
## Phase [N] Implementation Summary
**Completed by implementer agent:**
- [List of completed tasks]
**Automated verification results:**
- [Results of automated checks you performed]
**Manual verification required:**
- [List manual checks the human needs to perform]
Ready to proceed to Phase [N+1] after manual verification, or let me know if any issues need addressing.
Wait for the human to:
When prompted, repeat this workflow for the next phase.
If resuming work on a partially completed plan:
If the implementer agent reports a mismatch or gets stuck:
If instructed to implement multiple phases consecutively:
Workflow checklist:
When ALL phases are complete and verified (all checkboxes marked, all automated tests pass):
Read({SKILLBASE}/references/implement_plan_final_answer.md)
When invoked:
Remember: Your role is orchestration and verification. The implementer agent does the actual implementation work. Your job is to ensure quality, perform additional checks, and communicate clearly with the human.