rapid-implementlisted

# Rapid Implement Implement the assigned task with adaptive rigor. Process weight scales to task complexity. ## Phase 0: Classify (< 1 minute) Read the task requirements. Classify complexity: | Signal | Trivial | Moderate | Complex | Epic | |--------|---------|----------|---------|------| | Files touched | 1-2 | 2-4 | 5-10 | 10+ | | New models/tables | 0 | 0-1 | 1-3 | 3+ | | Concurrency needed | No | No | Maybe | Yes | | Cross-component | No | No | Yes | Yes | | Design decisions | 0 | 1-2 | 3-5 | 5+ | **Trivial/Moderate**: Note classification mentally. Skip to Phase 1. **Complex/Epic**: Write classification to `todos/rapid/PLAN.md`: ```markdown ## Classification: [Complex|Epic] ## Rationale: [1-2 sentences with signals observed] ## Files to modify: [list] ## Key risks: [list] ## Verification: [test command from requirements] ## Spec Checklist (enumerate EVERY item) ### Components/Subcommands/Endpoints: - [ ] [list each one from the spec] ### Architectural Constraints: - [ ] [e.g., "must call REST API, not direct DB access"] ### Flags/Options per component: - [ ] [list each flag from the spec] ``` **GATE 0** (Complex/Epic only): PLAN.md exists with classification AND complete spec checklist. Every subcommand, endpoint, flag, and architectural constraint from the spec must be enumerated. Missing items in the checklist = missing features in the implementation. ## Phase 1: Investigate (Adaptive) **Trivial**: Read the target file(s) directly. No investigation phase. **