Evolve Feature

Use this skill when an existing canonical feature needs to change and you want a durable, reviewable change packet instead of ad hoc edits to the baseline planning docs.

Responsibilities

1. Resolve the canonical feature planning folder under the repository planning layout.
2. Initialize the feature-local changes/ registry when it does not exist yet.
3. Create one change packet under docs/features/<feature-slug>/changes/<change-id>/.
4. Maintain machine-readable metadata for change lifecycle state.
5. Enforce the MVP rule that one canonical feature has at most one active open change at a time.

Preferred Input

• a canonical feature slug, folder name, or path
• a change ID or short slug
• an optional change type such as additive, narrowing, superseding, or replacement
• an optional summary of why the feature is changing