What problem does it solve?
This Skill removes uncertainty about which feature owns which parts of the codebase by providing a single source of truth (feature manifests) that link feature IDs to implementation files, tests, dependencies, and changelog entries. It prevents stale or orphaned code, improves release traceability, and makes it easier to validate feature completeness before shipping.
Core Features & Use Cases
- Manifest creation & updates: Create new feature manifests before implementation and update manifests as files and tests are added or changed.
- Code-to-feature mapping: Discover which feature owns a file or directory and list all implementation files, entry points, and related tests.
- Validation & health checks: Run automated manifest validation, detect stale or orphaned features, and surface missing tests or inconsistencies for release readiness.
- Use case: A developer implementing a new payment flow creates the manifest first, implements code and tests, runs validation and health checks, and appends a changelog entry so release engineers can verify feature completeness.
Quick Start
Ask the assistant to list all features and their implementing files using the repository's feature info and validation scripts so you can identify ownership and health at a glance.