execute-planlisted

Use this skill when the user says things like "execute the plan", "build task 2.1", "start phase 2", "continue building this module", "implement the next task", "work through the plan", or is ready to write code against a plan file that already exists. Not for creating a project's agent docs or its roadmap — use scaffold. Not for cutting a module into phases or re-planning one — use plan-module. Builds a module from the plan file `plan-module` wrote — `docs/guides/feature_[module]_plan.md` — in a strict micro-loop. Implement exactly one task, write the test code its plain-English scenarios describe, run it until green, then update the plan file before touching the next task. Stops at every phase verification gate to report and ask. Keeps closed counts, the Progress Log, Files Modified, and `docs/development-roadmap.md` statuses true as it goes.
melconcoast/code-idea · ★ 1 · Data & Documents · score 75

Install: claude install-skill melconcoast/code-idea

# execute-plan Builds a module from its plan file one task at a time — real code, real tests, actually run — and keeps the plan file and the roadmap true as it goes. ## When this runs - A `docs/guides/feature_<module>_plan.md` exists and the user is ready to build it - Work resumes on a plan already partly closed — pick up at the first open task, never restart - Never as a project's first step. No plan file means there is nothing to execute: hand off to `plan-module`, or to `scaffold` if there's no `docs/development-roadmap.md` either ## Core philosophy — hold these through every loop - **One task, then verify, then write.** Implement exactly one development task and the scenarios beneath it, get them green, update the plan file, and only then look at the next task. Batching a phase is how a plan file stops matching the code it claims to describe. - **`[x]` means verified, not written.** A task whose code exists but whose scenarios never ran is still `[ ]`. Never close an item on inspection, on intent, or on a type-check alone — something has to have actually run. - **The plan file is updated in the same pass as the code, not at the end.** If the loop is interrupted after code lands and before the file is written, the plan lies about what exists — and the next agent trusts it. - **A roadblock is a reframe, never a deletion.** When an approach doesn't survive contact, mark the task `[~]` with its reason and the replacement, and say so out loud. Silently dropping a task eras