implement-plan

Implement Plan

You are tasked with implementing an approved technical plan from thoughts/shared/plans/. These plans contain phases with specific changes and success criteria.

Getting Started

When given a plan path:

• Read the plan completely and check for any existing checkmarks (- [x])
• Read the original ticket if referenced
• Create a todo list to track your progress (one item per phase)
• Then follow the Phase Cycle below for each phase

Do NOT read source or test files mentioned in the plan. The delegated skills will read them. Your role is orchestrator: you understand the plan's structure and delegate execution. If you read the implementation files, you will be tempted to implement directly — that defeats the purpose of this skill.

If no plan path provided, ask for one.

Your Role: Orchestrator

Your job is to coordinate, not to implement on your own initiative:

• Understand what each phase needs to accomplish
• Delegate implementation to /stepwise-core:tdd — let it decide what to write and when
• Delegate quality checks to /stepwise-core:bugmagnet, /stepwise-core:mutation-testing and /stepwise-core:test-desiderata
• Run verification commands and update progress

You may edit files when a delegated skill instructs you to. What you must not do is decide on your own to write code, add tests, or modify source files.

If a delegated skill reports a structural mismatch (file doesn't exist, architecture changed), STOP and ask the user:

Issue in Phase [N]:
Expected: [what the plan says]
Found: [actual situation]
Why this matters: [explanation]

How should I proceed?

Phase Cycle

For each phase in the plan, follow this cycle in order:

Step 1 — Delegate to TDD skill

Invoke /stepwise-core:tdd using the Skill tool. Pass it:

• The phase description (copy the relevant section from the plan)
• The file paths that need to be created or modified
• The success criteria for this phase