/build-plan

Source: ~/.claude/skills/build-plan/SKILL.md

---

name: build-plan version: 2.0 description: > Execute an approved plan using TaskList with builder/validator teams. RunUse after /plan-with-team.team creates an approved plan. Triggers: "execute the plan", "build this", "implement the plan", "run the plan", "/build-plan". argument-hint: "[path to plan file, or leave empty for latest]latest in ~/system/specs/]" level: 3

Build/build-plan — Execute Approved Plan

Purpose

ExecuteExecutes a pre-approved plan file using the TaskList system withparallel builder/validator teams.

TaskList

Instructions

agents.

YouRun areAFTER executing/plan-with-team — never execute without an approved plan.

Variables

creatingspawningagents.

Variable	Type	Description	Default
plan_path	path	Path to plan byfile	latest tasksin and~/system/specs/
concurrency	number	Parallel builders	3
yolo	flag	Skip browser testing	false

Workflow

Step 1: Load Plan

If

path
• if provided,$ARGUMENTS readprovided that→ file.use Otherwise,as plan_path
• else → find mostlatest recent .md inplan: ls -t ~/system/specs/*.md | head -1.

  Extract:

  • Team members (builders and validators)
  • TasksRead withplan file, verify it has: [ ] task checkboxes + acceptance criteria
  • Dependencies (blockedBy)

  Step 2: CreateValidate TasksPrerequisites

  For

  each
  • Check: taskdoes inplan thehave plan:
    approval

    marker? (TaskCreate({## subject:APPROVED "[Tasksection titleor fromstatus: plan]",approved)

  description:
  • if "[Fullnot descriptionapproved +→ acceptanceSTOP, criteria]",tell activeForm:user "[Presentto tenserun action,/plan-with-team e.g.,first
  'Building
  • Check: authare module']"required })services running? (DB, relevant tools)

  Step 3: SetActivate DependenciesBuild Mode

  node ~/system/tools/build-mode.js start <project_dir> --concurrency <N>
  

  Builder completion flow

  ForBuilders eachcall node ~/system/tools/mc.js ready <id> NOT mc.js done. Only after Proveo/validator task,verification blockcan ittasks bybe itsmarked builder:done. Build-plan CANNOT report COMPLETE until all tasks pass Proveo verification.

  TaskUpdate({
    taskId: "[validator-id]",
    addBlockedBy: ["[builder-id]"]
  })
  

  Step 4: Execute BuildersTasks (Parallel)parallel where independent)

  For alleach unblocked[ ] task in plan:

  • if task has no dependencies → spawn in parallel with builder tasks,agent
  spawn agents IN PARALLEL using Task tool:

  Task({
    subagent_type: "general-purpose",
    description: "Build [component]",
    prompt: `You are a BUILDER agent. Read ~/.claude/agents/builder.md.
  
  Your
  if task ID:has dependencies → wait for dep completion, then spawn
  
  Each builder: reads task spec, implements, marks [id]x] Task:when [description]done
  Acceptance criteria: [criteria]
  
  When done, report what you built.`
  })
  

  Step 5: UpdateValidate BuilderEach StatusTask

  WhenAfter builderseach complete:task completes → spawn validator agent:

  TaskUpdate({
  
  taskId:
  Runs "[id]",tests status:relevant "completed"to })task
  

• Checks acceptance criteria
• if FAIL → send back to builder with failure context
• if PASS → proceed

Step 6: ExecuteFinal Validators (Parallel)Check

Spawn

validator
• All agentstasks for[x]? → run full test suite
• if PASS → node ~/system/tools/build-mode.js stop --status completed
• if FAIL → node ~/system/tools/build-mode.js stop --status failed + report

Report Format

BUILD-PLAN EXECUTION REPORT
Plan: [filename]
Status: [COMPLETE|PARTIAL|FAILED]
Tasks: X/Y completed
builders:

Task({
  subagent_type: "general-purpose",
  description: "ValidateTests: [component]",passing/total]
prompt: `You are a VALIDATOR agent. Read ~/.claude/agents/validator.md.

Your task ID:Duration: [id]time]
Task:Issues: [description]any Check: [acceptance criteria]

READ-ONLY. Report PASSblockers or FAIL.`
})

Step 7: Update & Report

When all tasks complete, show:

# Build Complete

## Summary
- Total tasks: X
- Passed: Y
- Failed: Z

## Tasks
- [x] Task 1 — PASS
- [x] Task 2 — PASS
- [ ] Task 3 — FAIL: [reason]

## Files Created/Modified
[list]

## Next Steps
[if failures]

Rules


Parallel execution — Launch independent tasks together

Respect dependencies — Never skip blockedBy

Report failures — Don't hide issues


$ARGUMENTS