/build Orchestrator
Purpose
Implement the current plan artifact exactly, honoring phases, tasks, owners, and gates.
Preflight conformance checks
- Plan
Status is Approved (or explicit override logged in Decision Log). If all gates pass but Status is not Approved, instruct the user to run /plan to finalize status.
- Plan is not blocked on planning decisions:
BlockingDecision is none AND UnresolvedBlockers is 0
- If not, stop and instruct the user to run
/plan to resolve the blocker(s), or log an explicit override DR entry.
- Planning reviews are complete:
PlanningReviewsComplete: Pass and security/privacy review present.
- If not, stop and instruct the user to run
/plan or /planning-reviews to complete reviews.
- Identify current phase, tasks, owners, exit criteria, and gates.
- Identify dependencies, merge points, and allowed parallel workstreams.
- Conformance for parallelism:
- Each file delta has a single explicit owner (WS/agent) until an explicit merge point.
- If multiple workstreams would touch the same file, require an integration task at a merge point and treat that file as owned by the integrator.
- If build discovers missing plan detail that changes intent (interfaces, invariants, scope, rollout, tests), stop and require a plan patch + DR entry (do not redesign silently during build).
- If ambiguity exists, stop and require a plan patch + DR entry.
User experience rule (no "go read the plan")
- If build is blocked (ambiguity, missing decision, missing gate definition), paste the relevant excerpt(s) in the chat response:
- the phase/tasks that are blocked
- the exact missing decision or missing plan detail
- the recommended minimal plan patch to unblock
Execution model
- Phases are serial.
- Workstreams can be parallel only if the plan says so.
- Merge points are explicit steps that integrate parallel work.
Build-time gates
- Lint/format, unit tests, integration tests, smoke/manual steps, build artifacts, staging dry-run.
- Run only gates listed for the phase.
Output format
Update the current plan artifact with this block:
## Execution Status
Phase: <name>
Status: not started | in progress | blocked | complete
Workstreams:
- WS1: <status> - completed tasks / blockers
- WS2: ...
Completed tasks:
- ...
Blocked:
- ... - reason - requires DR-xxx / plan patch
Build gates:
- Lint - pass/fail - notes
- Tests - pass/fail - notes
Next actions:
- ...
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: build-113description: Execute the current plan artifact exactly with plan-execution discipline and build-time gates. Use when the user runs /build or requests implementation from an approved plan. Use when this capability is needed.4---56# /build Orchestrator78## Purpose9Implement the current plan artifact exactly, honoring phases, tasks, owners, and gates.1011## Preflight conformance checks12- Plan `Status` is Approved (or explicit override logged in Decision Log). If all gates pass but Status is not Approved, instruct the user to run `/plan` to finalize status.13- Plan is not blocked on planning decisions:14 - `BlockingDecision` is `none` AND `UnresolvedBlockers` is `0`15 - If not, stop and instruct the user to run `/plan` to resolve the blocker(s), or log an explicit override DR entry.16- Planning reviews are complete:17 - `PlanningReviewsComplete: Pass` and security/privacy review present.18 - If not, stop and instruct the user to run `/plan` or `/planning-reviews` to complete reviews.19- Identify current phase, tasks, owners, exit criteria, and gates.20- Identify dependencies, merge points, and allowed parallel workstreams.21- Conformance for parallelism:22 - Each file delta has a single explicit owner (WS/agent) until an explicit merge point.23 - If multiple workstreams would touch the same file, require an integration task at a merge point and treat that file as owned by the integrator.24- If build discovers missing plan detail that changes intent (interfaces, invariants, scope, rollout, tests), stop and require a plan patch + DR entry (do not redesign silently during build).25- If ambiguity exists, stop and require a plan patch + DR entry.2627## User experience rule (no "go read the plan")28- If build is blocked (ambiguity, missing decision, missing gate definition), paste the relevant excerpt(s) in the chat response:29 - the phase/tasks that are blocked30 - the exact missing decision or missing plan detail31 - the recommended minimal plan patch to unblock3233## Execution model34- Phases are serial.35- Workstreams can be parallel only if the plan says so.36- Merge points are explicit steps that integrate parallel work.3738## Build-time gates39- Lint/format, unit tests, integration tests, smoke/manual steps, build artifacts, staging dry-run.40- Run only gates listed for the phase.4142## Output format43Update the current plan artifact with this block:4445```md46## Execution Status47Phase: <name>48Status: not started | in progress | blocked | complete4950Workstreams:51- WS1: <status> - completed tasks / blockers52- WS2: ...5354Completed tasks:55- ...5657Blocked:58- ... - reason - requires DR-xxx / plan patch5960Build gates:61- Lint - pass/fail - notes62- Tests - pass/fail - notes6364Next actions:65- ...66```6768---69> Converted and distributed by [TomeVault](https://tomevault.io/claim/atlas-memory-framework) — claim your Tome and manage your conversions.70<!-- tomevault:4.0:skill_md:2026-04-13 -->