What problem does it solve? Turning an approved specification into working code without a structured plan leads to missed requirements, vague tasks, and inconsistent commits. This Skill converts an approved spec into a detailed, test-driven implementation plan with exact file paths, full code, and verification commands. ## Core Features & Use Cases - Spec-to-Plan Conversion: Reads an approved spec from .project/docs/specs/ and produces a timestamped plan in .project/docs/plans/ with a mandatory header, architecture summary, and global constraints. - Bite-Sized TDD Tasks: Decomposes work into tasks where each task is one TDD cycle — failing test, verification command, minimal implementation, and commit — with no placeholders allowed. - Scope and Quality Gates: Runs a pre-flight make check baseline, proposes splitting multi-subsystem specs into separate plans, and self-reviews for spec coverage, placeholders, and type consistency. - Execution Handoff: Creates the feature branch and offers subagent-driven parallel execution in worktrees or inline execution with commons:tdd. - Use Case: After approving a spec for a new API endpoint, invoke this Skill to get a plan file where every task contains the actual test code, implementation code, and commit commands an engineer (or subagent) can execute directly. ## Quick Start Ask the assistant to create an implementation plan from the approved spec in .project/docs/specs/ using the plan skill.
