How does the skill handle completed features?

Once all TODOs are finished and acceptance criteria are met, the skill uses a Python script to move the plan to the `doc/plan/achieved/` folder with a completion stamp.

Where are the feature plan files stored?

Plans are stored in the `doc/plan/` directory using a standardized `{feature-name}-plan.md` naming convention.

Can I customize the plan structure?

Yes, the skill is designed to pull from a `plan-template.md` file, allowing you to define the specific sections and requirements for your project.

Are there any technical requirements for archival?

Archiving requires Python 3.7+ to run the `archive_plan.py` script and appropriate write access to the documentation folders.

Does it support naming normalization?

Yes, the skill automatically converts ambiguous or poorly formatted names into clean kebab-case to ensure consistent file organization.

Feature Plan Manager

Name: Feature Plan Manager
Author: austinjan

byaustinjan

Productivity & Workflow

Automates the creation, tracking, and archiving of structured feature plan documents to streamline the software development lifecycle.

About

The Feature Plan Manager skill provides a structured framework for managing the entire lifecycle of a feature within a repository. By standardizing the creation of markdown-based plans in a dedicated directory, it ensures that developers consistently capture goals, requirements, risks, and milestones. The skill automates progress tracking through TODO list management and utilizes a specialized archival process for completed features, keeping the active workspace clean while maintaining a permanent record of development decisions.

Key Features

Automated kebab-case naming conventions and directory organization
Dynamic progress tracking with TODO/DONE list synchronization
0 GitHub stars
Automated archival of completed feature plans to a dedicated directory
Standardized plan creation using customizable markdown templates
Comprehensive review of requirements, dependencies, and acceptance criteria

Use Cases

Reviewing the status of an ongoing feature to identify missing requirements or references
Archiving completed feature documentation once all acceptance criteria are met
Starting a new feature by generating a structured plan with goals and milestones

About

Key Features

Automated kebab-case naming conventions and directory organization
Dynamic progress tracking with TODO/DONE list synchronization
0 GitHub stars
Automated archival of completed feature plans to a dedicated directory
Standardized plan creation using customizable markdown templates
Comprehensive review of requirements, dependencies, and acceptance criteria

Use Cases

Reviewing the status of an ongoing feature to identify missing requirements or references
Archiving completed feature documentation once all acceptance criteria are met
Starting a new feature by generating a structured plan with goals and milestones