feature-build
Feature Build Skill
Orchestrates the complete feature development lifecycle with clear phases, entry/exit criteria, and conversation loop patterns. This skill transforms feature requests into shipped, tested, and documented code.
Philosophy
Core Principles
-
Acceptance Criteria First — Define what "done" looks like before writing code. Testable criteria prevent scope creep and enable verification.
-
Components Live in Style Guide — Every UI component starts in the style-guide page. This ensures reusability, documents all states, and provides a living reference.
-
Test What You Build — Use browser tools to verify each step. Don't wait until the end to discover issues.
-
KISS (Keep It Simple, Stupid) — Implement the simplest solution that meets the criteria. Avoid over-engineering.
-
Loop Back, Don't Push Forward — When something doesn't work, return to the appropriate phase rather than patching around issues.