What problem does it solve? Adding a new feature to an existing keel documentation-driven project risks breaking numbering continuity, traceability chains, and document consistency. This Skill coordinates the incremental update of requirements, system design, test cases, and dev tasks so new features extend the existing F/US/AC/T numbering without collisions or gaps. ## Core Features & Use Cases - Three-tier mode detection: Automatically classifies a feature request as Lite, Standard, or Deep based on impact signals (cross-module changes, security relevance, core data model changes) and adjusts document scope and verification strength accordingly. - Stepwise orchestration with sub-agents: In full mode, delegates requirements, design, test-case, and task updates to dedicated skills via isolated sub-agents, passing only YAML summaries and ID lists between steps. - Baseline project support: Works with projects that only have a 00-baseline.md (created by retrofit), creating 01-requirements.md starting from F-001. - Use Case: You have an existing keel project and want to add a user preference module. Run the feature skill with a description; it detects a Standard-mode change, appends new F/US/AC entries, updates the design and test docs with traceability, splits dev tasks, and optionally hands off to dev-workflow for implementation. ## Quick Start Ask the AI to add a new feature to your existing keel project by running /feature followed by a short description of the functionality you want.
