implement-feature

Feature implementation from an approved plan requires loading the plan file and executing tasks in a disciplined sequence. This skill coordinates pre-flight, execution, and post-approval steps to turn the plan into a working feature.

Tracking development tasks during feature implementation is handled via a task.md file. This ensures disciplined task execution and traceability while progressing through the structured workflow phases.

Plan-driven development validates feature implementation quality through built-in quality gates. The workflow performs lint, build, and self-checks during execution to ensure alignment and reduce errors.

Yes, an approved implementation_plan.md file is required before starting structured feature development. The skill loads this plan to execute tasks in a disciplined sequence with clear checkpoints.

Documentation for stakeholders is generated by creating a walkthrough document upon feature completion. This final handoff artifact captures decisions and outcomes from the implementation workflow.

Plan-driven feature implementation workflows are limited to executing pre-approved plans and cannot design features from scratch. They rely entirely on the existence and quality of the input implementation_plan.md file.