/kbd-new-child
Create a child phase owned by the currently-active node.
OpenSpec lifecycle preflight
Before this stage, follow the orchestrator preflight: use the pinned OpenSpec 2.0.0 CLI through the managed runner — session start runs the read-only verify; phase entry runs refresh, which updates existing KBD/OpenSpec projects — then use that same runner for OpenSpec commands. Retry a pending phase-entry refresh before OpenSpec work; preserve authored specs and task state. Phase scripts run this automatically, including canonical-runtime paths.
What this does
- Validates the active waypoint has a resolvable node.
- Validates the child name (kebab-case, no traversal, no slashes) and refuses duplicates.
- Creates
.kbd-orchestrator/phases/<parent>/children/<child-name>/withgoals.md,progress.json,handoff-in.md(parent→child contract), andscope.json(context-isolation contract). - Atomically appends
<child-name>tochildPhases[], setschildPointerto the new child, updatescurrentTaskandexactNextCommandto scope to the child. - Fires
child:beforeexactly once for the new child. - Emits Progress Signals and a confirmation banner.
When to use
When a phase (or child) reveals work that's complex enough to deserve its own
scope but not big enough to be a sibling phase. Each child carries its own
assessment.md / plan.md / execution.md / reflection.md under
phases/<parent>/children/<child>/.
Compare to /kbd-new-phase, which creates a top-level sibling.
Progress Signals (MANDATORY)
Starting kbd-new-child — <parent>/<child>
Completed kbd-new-child — <parent>/<child> ready for /kbd-assess
Prerequisites
- A node MUST be active (the waypoint's resolvable path is non-empty).
- The proposed child name MUST NOT already appear in
childPhases[]. current-waypoint.jsonMUST be valid JSON.- The new depth MUST NOT exceed
project.json'smaxChildDepth(default 4).
How to invoke
node scripts/kbd-new-child.mjs <child-name> [goal-1] [goal-2] …
Examples
/kbd-new-child auth-refactor "split user-model" "migrate sessions"
/kbd-new-child docs-sweep
/kbd-new-child perf-pass-1
Hook integration
Fires child:before exactly once, after the waypoint flip, so hooks
reading state see the new child as authoritative. The hook's index is the
1-based depth of the new child; total is the configured maxChildDepth.
Selected-method recovery and authority
Before dependent work, run node <pack-root>/scripts/kbd-method-context.mjs --project <project-root> --phase <canonical-phase-id> --write (or read the phase-local method-context.md when Node is unavailable) and act on its status:
RESOLVED_REFERENCES— continue with the recovered method, contract and stage authority; preserve the same references in role inputs, dispatch and handoff read order.BLOCKED— the contract, its binding, a calibration reference, a supersession or a deviation's cadence/reason is missing or changed, or canonical status is unavailable; resolve it explicitly. Prior commands, memory and tool inventories are not fresh authority.CONFLICT— a governing rule file the active harness loads grants an exception VLBV forbids (for example a compiler check or an hourly integration gate during generation). Stop before dependent work and show the conflict; continue only after the operator records aKBD-POLICY-ACKdecision for that file's current hash. Never rewrite operator-owned policy, and never treat an exception as authority for tests, builds, dry-runs or generated-code verification.
VLBV is the method for every phase (project default verificationMethod: "VLBV"); a deviation exists only as a signed KBD-METHOD decision naming the method, its execution cadence and its reason, and it is disclosed in the closure packet. Define acceptance before generation; generated code executes only at the value-phase boundary (B4) and, after an authorized repair, at B5 — see kbd-process-orchestrator/references/boundaries.md. Tasks, hours, commits, reviewer requests and compiler problems create no boundary. Preserve original evidence, consumed budgets and unresolved effects across resume and supersession; reconcile an uncertain effect before any retry. Full rules: kbd-process-orchestrator/references/method-context.md.