plan-management
Apply project planning conventions when creating or organizing plans. Use when user asks to create a plan, add a feature plan, document a bug, or work with the plans/ directory.
When & Why to Use This Skill
The Plan Management skill streamlines project organization by enforcing standardized conventions for creating, documenting, and tracking development plans. It ensures consistency across feature requests, bug fixes, and technical designs by automating directory structures, numbering systems, and status updates within the codebase.
Use Cases
- Initiating new features: Automatically generate structured plan templates with clear sections for problem statements, proposed solutions, and implementation steps to ensure technical alignment.
- Bug tracking and documentation: Systematically record bug investigations and fixes within a dedicated directory, maintaining a searchable history of resolved issues.
- Proactive roadmap maintenance: Automatically update plan statuses to 'Complete' and generate implementation summaries after finishing tasks to keep project documentation in sync with the actual code.
- Organizing complex codebases: Maintain a clean and navigable 'plans/' directory using specific categories like model, visuals, and gameplay to help teams quickly locate relevant architectural decisions.
| name | plan-management |
|---|---|
| description | Apply project planning conventions when creating or organizing plans. Use when user asks to create a plan, add a feature plan, document a bug, or work with the plans/ directory. |
Plan Management Conventions
This project uses a structured planning system. Apply these conventions when working with plans.
Directory Structure
| Folder | Purpose |
|---|---|
plans/model/ |
Wave physics, simulation, timing |
plans/visuals/ |
Rendering, gradients, effects |
plans/gameplay/ |
Surfer, controls, multiplayer |
plans/tooling/ |
Debug panel, dev tools |
plans/testing/ |
Test strategy |
plans/bugfixes/ |
Bug investigation and fixes |
plans/world/ |
Environmental systems |
plans/reference/ |
Research docs (never archive) |
plans/archive/ |
Superseded plans |
Numbering Convention
- Use increments of 10 (10, 20, 30...) to allow inserting related plans
- Check existing files in target folder to find next available number
- Preserve numbers when moving plans between folders
Plan Template
# Plan [NUMBER]: [Title]
**Status**: Proposed | In Progress | Blocked | Complete
**Category**: model | visuals | gameplay | tooling | testing | bugfixes
**Depends On**: [other plan numbers, if any]
## Problem
Clear statement of what needs to be solved.
## Proposed Solution
Technical approach and key design decisions.
## Implementation Steps
1. First step with clear acceptance criteria
2. Second step...
## Files Affected
- `src/file.js` - What changes needed
## Testing
How to verify the implementation works correctly.
Updating Plans After Implementation
When completing implementation steps from a plan:
- Update status - Change
**Status**: Proposedto**Status**: Complete(orIn Progressif partially done) - Add completion summary - Add a
## Completion Summarysection at the end documenting:- What was implemented
- Any deviations from the original plan
- Files that were actually modified
- Do this proactively - Update the plan immediately after finishing, without waiting for user to ask
When to Apply
Automatically apply when:
- User says "create a plan", "add a feature", "document this"
- Working with files in
plans/directory - User references plan numbers or categories
- Completing implementation of a plan (update status and add summary)