| name | managing-feature-plans |
| description | Creates or updates feature implementation plan documents in doc/plan. Use when planning a new software feature, refining feature scope/name, tracking TODO/DONE progress, or marking a plan as achieved. |
When to use this skill
- User asks to implement a new feature, plan a feature, or refine a feature scope.
- User asks to review progress of a feature.
- User asks to review an existing feature plan's requirements, references, and TODOs.
- User says a plan is done and should be archived as achieved.
This skill is idea for:
- Creating/Review feature plans as part of development process.
- Establish trackable, meaningful feature progress and documentation.
- Automating the feature development process.
Key Features
- Feature Plan Creation
- Creates properly formatted feature plan documents in
doc/plan/{feature-name}-plan.mdsee template fileplan-template.md - Writes Plan content to file path:
doc/plan/{feature-name}-plan.md - Enforces naming conventions, Plan file name format:
{feature-name}-plan.mdexamplestorage-interface-plan.md
- Review Feature Plan
- Confirms incomplete items, missing references, and TODOs.
- Modifies requirements and implementation tasks, TODOs.
- Updates existing feature plan documents with new information.
- Feature Plan Archiving
- Verifies feature plan completeness.
- Archives completed feature plans, move the plan to
doc/plan/archivedfolder example:doc/plan/archived/{feature-name}-plan.md.
How it Works
Resolve feature name
- If user provided a name: normalize to kebab-case.
- If name is ambiguous (e.g., "UI", "storage", "fix bug"): suggest better names and choose one.
Locate plan
- Check whether
doc/plan/{feature-name}-plan.mdexists. - If not exists: create it from
plan-template.md(or inline template if template file not available). - If exists: update it (append new info, re-scope, move items between TODO/DONE, keep changelog).
- Check whether
Review Content
- Fill/refresh: Goals, Non-goals, Requirements, Design, Milestones, Tasks.
- Capture dependencies, risks, and acceptance criteria.
- Maintain TODO/DONE lists with checkboxes.
Achieve
- If TODO is empty and acceptance criteria are met:
- Move plan file to
doc/plan/achieved/wiht python scriptarchive_plan.py
python archive_plan.py {feature-name}- Add a completion stamp in the plan (date + summary)
- Move plan file to
- If TODO is empty and acceptance criteria are met:
Requirements
- Python 3.7+ for archive_plan.py script.
- Write access to skill creation plan, and archived folder.
- Write access to create and update feature plan documents.
- Read access to feature plan documents.