What problem does it solve? Feature development without structure leads to implementation before requirements are understood, tests written after code, and security reviewed never. This Skill enforces a discovery-then-implement-then-deliver sequence with mandatory human checkpoints, parallel agent execution, and numbered artifacts so no phase operates without the output of its predecessor. ## Core Features & Use Cases - Phased Pipeline with Checkpoint Gates: Runs Discovery, Implementation, Review, and Delivery phases, each requiring explicit user approval before proceeding. - Parallel Agent Streams: Spawns backend, frontend, and test agents in parallel during implementation, plus security and performance review agents before delivery. - Numbered Artifact Chaining: Produces ten ordered artifacts (01-requirements.md through 10-final-checklist.md) in a .feature-dev/ directory, with a state.json tracking phase status and git refs for clean per-phase revert. - Use Case: When building a multi-layer feature like user authentication, use this workflow to gather requirements, design architecture, implement backend and frontend in parallel, run security and performance reviews, and generate deployment config and documentation with full traceability. ## Quick Start Ask Claude to run the feature-pipeline workflow to build your feature, starting with the discovery phase to gather requirements and architecture before any code is written.
