brewcode:start
Executes a brewcode task PLAN.md with infinite context and automatic session handoff (third pipeline step after spec and plan). Triggers: start brewcode task, execute PLAN.md, run task with handoff, infinite execution, brewcode start, execute brewcode plan, run the plan.
What this skill does
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: phases/{Phase File}\nTask dir: {TASK_DIR}\nArtifacts: artifacts/{Artifact Dir from Phase Registry}/\nKNOWLEDGE: KNOWLEDGE.jsonl",
activeForm = "{Present continuous of Subject}"
)
```
**Sub-step 4a: Phase-to-TaskID Map**
Task IDs are auto-incremented (1,2,3...) and may NOT match Phase # (1,1V,2,3...).
Build a map: `{phase# -> taskId}` during creation. Include phase # explicitly in description.
### 5. Set Dependencies
```
FOR each row where "Blocked By" column is non-empty:
TaskUpdate(taskId, addBlockedBy=[mapped task IDs from Blocked By column])
```
### 6. Execution Loop
```
LOOP while pending tasks remain:
a. TaskList() -> find tasks: status=pending, blockedBy=[]
b. Same Parallel group -> spawn in ONE message (parallel Task calls)
c. Per task:
i. TaskUpdate(taskId, status="in_progress")
ii. Task(subagent_type="{Agent from Phase Registry}", prompt from description)
-- If Phase Registry agent not found as plugin: check `.claude/agents/` for project/team agent
-- If agent REFUSED (Task Acceptance Protocol — returned refusal with colleague suggestion):
a. Re-delegate to suggested colleague agent (max 2 retries)
b. If no suitable colleague or retries exhausted: fall back to plugin agent
c. Log refusal to KNOWLEDGE.jsonl:
{"ts":"...","t":"ℹ️","txt":"Phase {N}: {agent} refused, re-delegated to {new_agent}","src":"manager"}
-- If agent FAILED (is_error=true):
a. TaskUpdate(taskId, status="in_progress") -- keep in progress for retry
b. Persist failure to KNOWLEDGE.jsonl:
{"ts":"...","t":"❌","txt":"Phase {N} agent failed: {error_summary}. Attempt {I}/{MAX}.","src":"manager"}
c. Retry once with same agent
d. If retry fails: TaskUpdate(taskId, status="failed"), apply Escalation table
e. Skip steps iii-v (no report to write, no coordinator to call)
-- If agent SUCCEEDED:
iii. WRITE report -> artifacts/{P}-{N}{T}/{AGENT}_output.md
iv. Task(subagent_type="brewcode:bc-coordinator",
prompt="Mode: standard. Task path: {TASK_PATH}. Report: {REPORT_PATH}")
-- If coordinator FAILED (is_error=true): log warning, proceed to TaskUpdate(completed)
v. TaskUpdate(taskId, status="completed")
d. On verification FAIL:
i. Read verification report from artifacts/{P}-{N}{T}/{VERIFY_AGENT}_output.md
(manager can read artifacts/ — the rule is NEVER read phases/)
Extract: {ISSUES_TABLE}, {FILES_TO_FIX} from the issues table in the report
{VERIFY_AGENT} = agent from the verification row in Phase Registry
{VERIFY_ARTIFACT_DIR} = artifact dir of the verification phase
ii. Write phases/{N}F{I}-fix-{name}.md using phase-fix.md.template
(from .claude/tasks/templates/ or $BC_PLUGIN_ROOT/skills/setup/templates/)
Fill: {PHASE_NUM}, {ITERATION}, {PHASE_NAME}, {FIX_AGENT}=original agent,
{ORIGINAL_PHASE_FILE}, {VERIFY_ARTIFACT_DIR}, {VERIFY_AGENT},
{ISSUES_TABLE} from verification report (step 6.d.i), {FILES_TO_FIX}, {ARTIFACT_DIR}
iii. TaskCreate(subject="Fix phase {N} issues (iter {I})", ...)
iv. TaskCreate(subject="Re-verify phase {N} (iter {I+1})",
addBlockedBy=[fix task ID])
v. Max 3 iterations -> Escalation
e. Deadlock check after each iteration:
TaskList() -> categorize:
- ready = pending + blockedBy=[]
- blocked = pending + blockedBy non-empty
- active = in_progress
If ready=0 AND active=0 AND blocked>0:
DEADLOCK -> cascade failure to all blocked tasks, BREAK -> Finalize(status="failed")
If ready=0 AND active=0 AND blocked=0:
ALL DONE -> BREAK -> Finalize(status="finished")
Else: continue loop
```
Escalation after repeated failures:
| After | Action |
|-------|--------|
| 1 fail | R&D task: explore root cause |
| 2 fails | Split phase into sub-phases |
| 3 fails | Upgrade model, reassign, AskUserQuestion |
### Failure Cascade
When escalation exhausted (task permanently failed):
1. TaskUpdate(failedTaskId, status="failed")
2. Persist to KNOWLEDGE.jsonl:
{"ts":"...","t":"❌","txt":"Phase {N} permanently failed: {reason}","src":"manager"}
3. Cascade: TaskList() -> for each task T where failedTaskId in T.blockedBy (transitive):
TaskUpdate(T.id, status="failed")
4. Log: "Phase {N} permanently failed. Cascaded to {count} dependent tasks."
5. Independent tasks (no dependency on failed task) continue normally
### 7. Finalize
```
Task(subagent_type="brewcode:bc-coordinator",
prompt="Mode: finalize. Task path: {TASK_PATH}. Status: {finished|failed}")
```
Status is "finished" when all tasks completed, "failed" when deadlock/cascade occurred.
### 8. Extract Rules (REQUIRED)
```
Skill(skill="brewcode:rules", args="{KNOWLEDGE_PATH}")
```
### 9. Prune Knowledge (REQUIRED)
```
Task(subagent_type="brewcode:bc-knowledge-manager",
prompt="mode: prune-rules\ntaskPath: {TASK_PATH}")
```
## Handoff (After Compact)
1. `TaskList()` -- current task state (source of truth)
2. Read PLAN.md -- protocol and Phase Registry
3. DO NOT read phases/ -- they are for agents
4. Continue with current `in_progress` or next `pending` task
5. WRITE report -> CALL coordinator after EVERY agent (ALWAYS)
</instructions>
Related in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.