← ClaudeAtlas

feature-filelisted

Manage features.yml for tracking requirements and progress; use proactively ONLY when features.yml already exists, or invoke manually to create one; complements TodoWrite for persistent project state.
aiskillstore/marketplace · ★ 329 · Data & Documents · score 79
Install: claude install-skill aiskillstore/marketplace
# Feature File Management Manage `features.yml` - a waterfall-style planning document combining structured requirements tracking with incremental development. ## Quick Reference ```yaml feature: "Feature Name" phase: Requirements | Design | Implementation | Testing | Complete version: 1 changelog: | ## [1] ### Added - Initial feature decisions: - Decision rationale known-issues: - Known bug or limitation requirements: req-id: description: "When X, the system SHALL Y" status: Not-Started | In-Progress | Needs-Work | Complete tested-by: [test-id] test-cases: test-id: name: "test_function_name" file: "tests/test_file.py" description: "Given X, when Y, then Z" passing: true | false type: unit | [integration, rainy-day] # optional, string or list --- # Next feature... ``` See `references/schema.md` for complete field documentation. ## Proactive Usage This skill should be used automatically when features.yml exists. ### Before Starting Implementation 1. Check if `features.yml` exists in project root 2. If missing: do not use this skill proactively (stop here) 3. **Plan the work in features.yml before writing code:** - Add/update the feature with all requirements extracted from the user's request - Add anticipated test cases to `test-cases` (with `passing: false`) - Document design decisions in `decisions` if non-trivial choices are involved 4. Set the first requirement to `status: In-Progress` ### During Implementatio