brewcodestartlisted

Execute Task — [task-file-path] <instructions> ## How It Works ``` /brewcode:start -> Load PLAN.md -> Parse Phase Registry | v TaskCreate for each row -> TaskUpdate dependencies | v Execution Loop: TaskList() -> pending+unblocked -> spawn agents | v Per agent: WRITE report -> CALL bc-coordinator (2-step, ALWAYS) | v TaskUpdate(completed) -> repeat -> Finalize | v After compact: TaskList() -> Read PLAN.md -> continue ``` ## Execution Steps ### 1. Resolve Task Path - If `$ARGUMENTS` has path -> use it - If `$ARGUMENTS` empty -> read `.claude/TASK.md` (first line = active path) - If neither -> STOP: `No task path! Run: /brewcode:spec "description" then /brewcode:plan` ### 2. Initialize via Coordinator (REQUIRED) ``` Task tool: subagent_type: "brewcode:bc-coordinator" prompt: "Mode: initialize. Task path: {TASK_PATH}" ``` Coordinator validates, creates lock, updates status -> `in progress`. - Suggest user run `/goal` (CC 2.1.115+) to anchor the session's objective before execution proceeds. ### 3. Load Context - Read PLAN.md (ONLY PLAN.md from the task directory) - Read KNOWLEDGE.jsonl if exists - Verify artifacts/ directory exists - DO NOT read phases/ files -- they are for agents, not the manager ### 4. Create Tasks from Phase Registry Parse the `## Phase Registry` table in PLAN.md. ``` FOR each row in Phase Registry: TaskCreate( subject = "Phase {#}: {Subject}", description = "Phase {#}: {Summary}\n\nFull instructions