Execute an implementation plan by writing code, task by task. Use after planning (or when the user provides a clear, ordered list of code changes to make). Works through tasks sequentially, follows codebase conventions, verifies as it goes, and checks in with the user at key decision points. Triggers: 'implement this plan', 'execute this plan', 'build this', 'start implementing', 'do the tasks'.
Execute an implementation plan by writing code, one task at a time.
This is NOT planning - the technical decisions should already be made. If the plan is missing critical details (which files, what approach), say so and suggest running the planning skill first rather than guessing.
This skill works best with an implementation plan from the planning skill (found in .plans/<feature-name>.plan.md). It also accepts any ordered list of code changes that specifies what files to touch and what to change.
If the input is just a vague idea or feature description, say so and suggest running the brainstorming or planning skills first.
Before writing any code:
Work through tasks in order. For each task:
If a task is large, break it into sub-steps and work through them. But don't break the plan's task boundaries - each plan task should result in a coherent, working state.
After all tasks are done:
These are the common situations where the plan meets reality: