superspec:plan

To generate an implementation plan from a validated spec, this Skill automates the creation of a structured plan.md and companion tasks.md. It converts validated specifications into bite-sized, test-first work items with clear traceability to design artifacts and requirements.

A test-first execution plan structures development tasks using a RED, GREEN, REFACTOR workflow for each item. This approach enforces bite-sized, test-driven development cycles and generates an auditable Run and Expected workflow integrated with execution processes.

To ensure traceability between design artifacts and implementation tasks, the plan-driven generation process explicitly links every bite-sized work item back to the validated specs. This creates an auditable track connecting your requirements directly to the test-first execution plan.

Yes, you need validated specs before creating a test-first execution blueprint. This Skill targets the specific development stage where teams must convert already validated specifications into concrete, trackable work items and structured plan documents.

Spec-based planning requires generating a Plan Document structure, typically named plan.md, alongside a companion tasks checklist named tasks.md. These files guide the test-first execution workflow and track commits according to the validated spec.

You should not use an automated plan-writing approach if your specifications are not yet validated or if your project does not require strict test-first, traceable task structures. It is specifically designed for converting validated specs into structured, auditable work items.