task-implementerlisted

# Task Implementer ## Purpose Receives a single atomic task (JSON task object from `issue-analyzer`) and implements it end-to-end. Designed to run autonomously as a sub-agent — no user interaction required. Commits its changes to a shared feature branch managed by the orchestrator. **Input:** JSON task object + workspace context (branch, codebase path, issue number) **Output:** JSON result object with implementation status, files modified, verification results ## When to Use - Orchestrator dispatches a task from `issue-analyzer` decomposition - Implementing a single atomic code change (new component, store change, API fix, etc.) - Fixing review findings dispatched back by orchestrator (`task_type: "fix"`) ## Architecture: 6 Phases ``` Phase 1: RECEIVE → Parse task input, validate, set up context Phase 2: RESEARCH → Deep-read target files, understand module patterns Phase 3: PLAN → Decide implementation approach, list file changes Phase 4: IMPLEMENT → Write code, tests, stories Phase 5: VERIFY → Run lint, type-check, tests Phase 6: REPORT → Write result file + emit compact STATUS response ``` --- ## Workflow ``` Task Implementer Progress: - [ ] Phase 1: Receive and parse task input - [ ] Phase 2: Research target files and module patterns - [ ] Phase 3: Plan implementation approach - [ ] Phase 4: Implement code changes - [ ] Phase 5: Verify (lint, type-check, test) - [ ] Phase 6: Report results ``` ### Phase 1: RECEIVE Parse the incoming ta