needs-implementation

To convert feature designs into working code, this Skill reads design.adoc and tasks.adoc artifacts to orchestrate phased code generation. It translates design specifications into functional code, executing implementation sequentially while maintaining alignment with the original feature requirements.

Phased feature implementation breaks the workflow into sequential stages, executing code generation for each phase and verifying builds and tests before committing. The Skill pauses for user prompts after each phase, ensuring incremental progress and design alignment before proceeding to the next stage.

Orchestrator-driven code generation requires a single feature package located at docs/features/<slug>/. You need docs/features/needs-implementation/tasks.adoc and design.adoc files present within this directory to guide the implementation workflow and provide the necessary design and task artifacts.

Yes, you can automate end-to-end feature implementation across multiple phases. The Skill orchestrates the entire workflow from reading task artifacts to generating code, verifying builds, and committing progress sequentially. It handles divergences by reporting them back to the orchestrator for resolution.

If generated code diverges from the original design, the Skill reports these divergences to the orchestrator. This mechanism ensures design alignment is maintained throughout the phased implementation, allowing for corrective adjustments without silently continuing with broken or misaligned feature code.