feature-development

Autonomous end-to-end feature development is orchestrated through a phased, gated workflow that manages complex implementation by invoking specialized skills for acceptance criteria, code scouting, ATDD building, and final verification. It enforces structured progression through mandatory development stages.

ATDD-based feature building is a core development stage within this workflow where implementation is guided by predefined acceptance criteria and sketched user scenarios. It operates autonomously by invoking specialized skills to construct features while enforcing validation gates before progression.

Complex feature implementation is structured into distinct mandatory stages: defining acceptance criteria, assessing existing code impact, sketching scenarios, building via ATDD, hardening code, and final verification. Built-in gates prevent skipping any step, ensuring rigorous validation throughout development.

Autonomous feature development supports substantial additions to existing functionality by analyzing the current codebase during a code scouting phase. It assesses impact and defines acceptance criteria before proceeding to sketch scenarios and build, ensuring new code integrates cleanly with existing modules.

Code quality is ensured through mandatory validation gates and a dedicated code hardening stage within the phased workflow. After ATDD-based building, the skill hardens the new code and performs final verification against initial acceptance criteria before completion.

A gated workflow should be used when building significant new features or substantial additions requiring rigorous validation across all phases. It prevents skipping steps like acceptance criteria definition, code scouting, scenario sketching, ATDD building, hardening, and final verification.