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