What problem does it solve? Turning a feature request into verified, committed code involves many failure-prone steps: misunderstood requirements, unverified assumptions about third-party dependencies, missing plans, and untested integrations. This Skill enforces a disciplined end-to-end workflow so features are analyzed, designed, implemented, tested, and committed with evidence at every stage. ## Core Features & Use Cases - Structured Requirements Analysis: Scores requirement completeness across four dimensions (goal clarity, expected outcome, scope, constraints) and asks targeted clarifying questions before design begins. - Feasibility Verification: Verifies third-party component capabilities, configuration keys, and protocol behaviors using read-only evidence (decompilation, reflection, minimal reproduction) instead of assumptions. - Planning Documents: Produces a proposal/design/tasks three-document set with checkbox-tracked tasks when the change spans modules or requires multiple iterations. - Layered Implementation & E2E Verification: Implements bottom-up (model → service → controller → frontend) with compile, unit test, and browser-MCP end-to-end verification, then commits via conventional git commits. - Use Case: A user asks to add a new API endpoint spanning backend and frontend. The Skill analyzes the requirement, verifies external dependencies, drafts a plan for confirmation, implements layer by layer, validates through the real browser link, and commits locally. ## Quick Start Ask the agent to take this new feature requirement from analysis through implementation, end-to-end verification, and a local git commit using the feature-dev workflow.
