feature-trackinglisted

# Feature Tracking Skill Track feature implementation status against requirements documents using hierarchical FR codes. ## When to Use This Skill | Use this skill when... | Use blueprint-feature-tracker-sync instead when... | |---|---| | You need to read or update feature implementation status by FR code | You want to reconcile TODO.md checkboxes with the tracker | | You're recalculating completion percentages mid-development | You want to drain WO entries from a taskwarrior sidecar | | You manage hierarchical FR codes (FR1, FR1.2, FR1.2.1) | You want a markdown progress summary via `--summary` | | You add features or phases to feature-tracker.json | Use blueprint-feature-tracker-status to view stats without modifying | ## Overview The feature tracker maintains a JSON file that maps requirements from a source document (e.g., REQUIREMENTS.md) to implementation status. It supports: - **Hierarchical FR codes**: FR1, FR2.1, FR2.1.1, etc. - **Phase-based development**: Group features by development phase - **PRD integration**: Link features to Product Requirements Documents - **Task tracking**: Track in-progress and pending tasks (replaces work-overview.md) - **Sync targets**: Keep TODO.md in sync ## When to Run Run feature tracking operations when: - Feature implementation status changes - New PRD is added or completed - After major development milestones - Before generating status reports - Starting a new development phase ## Core Concepts ### Feature Status Each fea