groove-work-plan

Outcome

The codebase is researched for relevant patterns and constraints. A concrete implementation plan is written with ordered steps, file paths, and function names. Plan is captured as a task or doc.

Acceptance Criteria

• Plan references actual code patterns found in the codebase (not assumptions)
• Steps are ordered and specific enough to execute without ambiguity
• File paths and function names are named where known
• Edge cases are identified and handling is specified
• Stage task created in backend: YYYY-MM-DD, Plan

Constraints