requirement-change
Add or modify tasks in Implementation Plan. Use when user proposes new requirements, changes priorities, or adjusts existing task scope.
When & Why to Use This Skill
The 'requirement-change' skill is designed to maintain project alignment by dynamically updating implementation plans and task structures. It solves the problem of documentation rot by ensuring that new requirements, shifting priorities, and scope adjustments are immediately reflected in the project's roadmap, keeping the development workflow organized and transparent.
Use Cases
- Integrating new feature requests into an existing implementation plan without disrupting the current development phase.
- Re-prioritizing the task list when business goals shift, ensuring the most critical items are addressed first.
- Breaking down vague user feedback into concrete, independent, and testable tasks within a structured project overview.
- Managing scope creep by formally documenting changes in the project's Phase and Task sections to maintain a clear audit trail.
| name | requirement-change |
|---|---|
| description | Add or modify tasks in Implementation Plan. Use when user proposes new requirements, changes priorities, or adjusts existing task scope. |
Requirement Change
Instructions
When user proposes new requirements or changes:
- Review
docs/PROJECT_OVERVIEW.mdanddocs/Implementation Plan.mdto understand current task structure and priority order - Identify appropriate Phase/Task location for the change
- Create/modify tasks following these principles:
Each task must:
- Be independently completable and testable
- Deliver complete functionality that can be verified (avoid partial implementations that are untestable)
- Focus on functionality and requirements (not code details)
- Update Priority Order table if priorities change
- For large new features, consider creating a new Phase section
- Keep documentation concise—avoid redundancy to reduce AI context usage