STOP - Read before ANY tool call
Read _shared/skill-boilerplate.md first. It holds the guardrails read, the session gate rule, the user sim rule, the one-step rule, the gate check, and the user chat language rule. The steps below are skill-specific only.
Skill: orchestrate-develop
Trigger
Negative signal: applies as defined in _shared/skill-boilerplate.md; the skill-specific signals are listed below.
Invoke when the user asks for: /orchestrate-develop, orchestrate develop, /orchestrate-develop, or Orchestrated Delivery O3 after O2 handoff.
Required: full feature path or a specific PLAN/PLAN_NNN_*.md path under a story.
Outcome
- Pending PLAN step(s) executed via Agent children when
subagents=native(SPAWN.md), each following thesdd-developcontract (one PLAN step per child / invocation); whensubagents=noneor Agent unavailable → fallback handoff to manual/sdd-develop(parent never writes app code; never hard-fail) - Feature
CONTINUITY.mdupdated (phasedevelop, progress, typed next invoke, Memory-bank path + status) - When the operator asked to close the wave, handoff to
code-review(- singleor- multi-angle; skill asks if omitted). When the operator did not ask, do not start that validation or specialist loop; hand off only the next step / next story
Step 0 (required): Memory Bank Gate (MEMORY-BANK.md, policy auto) before building the step queue / spawning children. Resolve bank_root via STORAGE.md + STORAGE-RESOLUTION.md. CONTINUITY stays the feature phase/handoff source.
Step N (after code changes): when at least one develop child succeeded with app file changes, run memory-bank-init mode refresh-light at bank_root before final handoff (MEMORY-BANK.md Step N). Confirm in the user chat language first.
Parent orchestrator never writes application code, never marks multiple PLAN steps done in one child, and never bypasses sdd-develop gates (step_confirmed, tests before complete).
Alternative (always valid): user runs manual /sdd-develop - <portable-plan-path> - Step N without this skill (RF05 / CA5). Manual Classic SDD does not require memory-bank (CA7).
Mental map (ids unchanged): O3 ≈ apply (implement PLAN steps via sdd-develop). O1 ≈ explore; O2 ≈ FEATURE+PRD+CHANGE. See CHANGE-CONTRACT.md.
Evidence verifier (REQ-005 / CA4): children record features/NNN-slug/{USnn|TSnn}/EVD/ + STATE.md and run validate-evidence inside sdd-develop. Verifier ≠ O3 — do not use O3 / Agent parallelism as the evidence verifier mechanism (sequential script gate only). Levels: off | cheap | standard | strict. Contract: EVD-STATE-CONTRACT.md.
Living loop / TRACE (REQ-006 / CA5): at feature-wave close, children (or the final develop child) append features/NNN-slug/TRACE.jsonl and run converge → sync current → archive, then validate-trace -RequireArchiveComplete. Parent must not use O3 parallelism as the archive verifier. Contract: TRACE-ARCHIVE-CONTRACT.md.
Lazy-load (only when needed)
| When | Path (after syncing the active adapter) |
|---|---|
| Command playbook (step discovery after gates) | {{TOOLKIT_ROOT}}/skills/orchestrate-develop/references/command.md |
| Caveman Mode (if active) | {{TOOLKIT_ROOT}}/skills/_shared/caveman/CAVEMAN.md - Full cap |
| Pipeline Orchestrated Delivery, paths | {{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/PIPELINE.md |
Invocation contexts (direct vs orchestrated, IC-DIRECT-ORCHESTRATED) |
{{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/INVOCATION-CONTEXTS.md |
| Storage | {{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/STORAGE.md |
| Dynamic manifest / repository-global root resolution (only when resolving storage) | {{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/STORAGE-RESOLUTION.md |
| Step 0 Memory Bank Gate | {{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/MEMORY-BANK.md |
| Memory-bank create/refresh | {{TOOLKIT_ROOT}}/skills/memory-bank-init/SKILL.md |
| Develop contract (source of truth) | {{TOOLKIT_ROOT}}/skills/sdd-develop/SKILL.md + {{TOOLKIT_ROOT}}/skills/sdd-develop/reference.md |
| SESSION gates | {{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/SESSION.md |
| CONTINUITY template | {{TOOLKIT_ROOT}}/skills/_shared/templates/features/CONTINUITY.md |
| Reference index (routing only) | {{TOOLKIT_ROOT}}/skills/orchestrate-develop/reference.md |
| Process step detail (lazy) | {{TOOLKIT_ROOT}}/skills/orchestrate-develop/references/<section>.md |
| Execution modes (serial/parallel/manual; queue/claim) | {{TOOLKIT_ROOT}}/skills/orchestrate-develop/references/execution-modes.md |
| plan-acquisition (REQ-008 / CA3) | {{TOOLKIT_ROOT}}/skills/orchestrate-develop/references/plan-acquisition.md |
| Execution display (before each spawn and after each receipt) | {{TOOLKIT_ROOT}}/skills/sdd-develop/references/execution-display.md |
Develop modes continuous | step_by_step (007 REQ-009) |
{{TOOLKIT_ROOT}}/skills/orchestrate-develop/references/develop-modes.md |
| plan-contract + delivery-baseline (REQ-010) | {{TOOLKIT_ROOT}}/skills/orchestrate-develop/references/plan-contract.md |
| O3 paired baseline and delta/risk review (REQ-010) | {{TOOLKIT_ROOT}}/skills/orchestrate-develop/references/step-queue-spawn.md |
Spawn native vs fallback (capability subagents) |
{{TOOLKIT_ROOT}}/skills/_shared/agents/SPAWN.md |
| Agent subagent model (default omit; rare premium gate) | {{TOOLKIT_ROOT}}/skills/_shared/agents/SUBAGENT-MODEL.md |
| Code review (ask mode) | {{TOOLKIT_ROOT}}/skills/code-review/SKILL.md |
Never by default: do not preload references/command.md before Step -1 gates; do not preload sdd-develop + all developer guideline packs into the parent, or paste guideline bodies into develop children. Parent loads contracts and SPAWN; children load sdd-develop for their one step.
Progressive load: PIPELINE.md + STORAGE.md first; after gates load references/command.md for step discovery; fan-out to MEMORY-BANK.md at Step 0, SPAWN.md before spawn, sdd-develop contract into the child prompt path only, and one references/<section>.md per Process step — never full reference.md when a section file exists (SKILL-REFERENCE-RETRIEVAL.md).
Reference routing
| Situation | Path |
|---|---|
| Command playbook (step discovery) | references/command.md |
| Gate / Orchestrated Delivery | PIPELINE.md |
| Feature / PLAN / bank roots | STORAGE.md |
| Step 0 Memory Bank | MEMORY-BANK.md |
| Before Agent / fallback to manual develop | SPAWN.md |
| Child implement contract | {{TOOLKIT_ROOT}}/skills/sdd-develop/SKILL.md |
| Preconditions / Step 0 / Step N refresh-light | references/preconditions.md |
| Anti-bypass checklist (CA5) | references/anti-bypass.md |
| Step queue / spawn child / Agent skeleton | references/step-queue-spawn.md |
Step 5.5 post-implement verifier (verify_mode) |
references/step-verifier.md |
| Safe parallelism | references/parallelism.md |
| Execution modes (serial/parallel/manual + ledger) | references/execution-modes.md |
| plan-acquisition (canonical PLAN) | references/plan-acquisition.md |
Develop modes continuous | step_by_step |
references/develop-modes.md |
| plan-contract markers + delivery-baseline | references/plan-contract.md |
| CONTINUITY / handoff / stop conditions | references/continuity-handoff.md |
| Contract reuse / boundaries / invoke strings | references/contract-boundaries.md |
| Caveman / resolve feature / PLAN set | references/process-common.md |
| Must not (full) | references/must-not.md |
| Review handoff | {{TOOLKIT_ROOT}}/skills/code-review/SKILL.md |
Process
After gates: Read references/command.md for ordered step discovery (do not dump this Process section into child prompts). Then load references/<section>.md for the current step only — not full reference.md. Do not skip gates.
Step -1b - Caveman Mode (Full cap)
Apply Full caveman prefs when active. Read references/process-common.md § Process — Caveman (Full cap).
1. Gate check
Report the Step -1 gate checklist in chat. Load PIPELINE.md (Orchestrated Delivery) and SESSION.md. STOP if any gate unchecked. Ask the user for confirm before spawning the first develop child (question contract and ids: {{TOOLKIT_ROOT}}/skills/_shared/agents/QUESTIONS.md). That confirm has no written deadline: follow core/policy/guardrails.md § Open questions without a written deadline. Use the host interactive question when the host offers one; otherwise ask in text. Send no further message until the operator answers every pending question. Silence, timeout, and end of turn are not answers. After the answer, resume this skill until the spawn finishes or this skill declares a blocker with the cause. The required confirm before writes stays.
1b. Resolve invocation context
Load INVOCATION-CONTEXTS.md. This invoked orchestrate-develop skill runs as orchestrated (IC-DIRECT-ORCHESTRATED); every develop child handoff must include invocation_context: orchestrated (path cite only — no contract body dump). This route belongs to the active O3 invocation. It does not make a separate Classic/direct sdd-develop invocation orchestrated merely because a parent coordinates work, orchestrator_mode=always, or its PLAN changes O3 contracts.
2. Resolve feature / PLAN set (plan-acquisition)
Load STORAGE.md and STORAGE-RESOLUTION.md; resolve feature + bank_root; path sanitize; plan-acquisition for canonical PLAN path(s) or STOP if missing. Before queue parsing, session creation, claim, or specialist invocation, run the deterministic read-only artifact gate:
pwsh -NoProfile -File "{{TOOLKIT_ROOT}}/scripts/validation/Invoke-O3ArtifactPreflight.ps1" -FeatureRoot <feature-root> -PlanPath <canonical-plan> -RepoPath <repo-root> -SddRoot <sdd-root> -EmitStepTable
Any nonzero result is plan_stale / blocked: do not create or update a session, claim, or specialist (including an implementer specialist). Inspect the exact diagnostic and classify it before stopping. If the failure is a repairable PRD/PLAN/CHANGE structural or cross-artifact inconsistency with no unresolved material decision, automatically route correction through O2 (orchestrate-deliver) in this same invocation; O2's existing owner skills perform the correction and its approval/write gates. Do not ask the operator to rerun O2 or relay routine validator output. If a returned specialist authored the affected document, use a fresh bounded invocation under the same owner contract; never reuse the completed child. If the correction changes approved meaning, requires missing evidence/access, reveals a product/contract question, or the owner contract requires a human approval, stop only at that actual gate and ask for the specific input. After O2 reconciliation, reread canonical artifacts and rerun this preflight; only a passing result permits O3 to create/update a session, acquire a claim, or dispatch a code implementer. Never edit PRD/PLAN/CHANGE from O3 or weaken a validator. Re-run after checkpoint/CONTINUITY reconciliation and immediately before every subsequent effect; do not rely on an earlier snapshot. Only exact PLAN metadata Status=approved passes. Parse queue and dependency order exclusively from the saved PLAN; validate that its six related artifacts agree, then derive CONTINUITY from the saved and re-read PLAN. Report the validator's features_versioned state verbatim; false means local SDD files are unversioned and may not accompany commits/clones. Do not call them committed. Read references/plan-acquisition.md and references/process-common.md § Process — Resolve feature / PLAN set.
3. Step 0 - Memory Bank Gate
Follow MEMORY-BANK.md (policy default auto). Bank root = resolved bank_root - not under features/. Pass bank_path into every develop child as read-only Prior context. Read references/preconditions.md § Step 0 - Memory Bank Gate.
4. Build step queue (deps)
Parse pending steps; respect Deps; resolve execution mode (serial default) and develop pacing (step_by_step default | continuous); present the pending-only dispatch queue separately from the complete PLAN-step table; wait for confirm. The execution-mode question (serial | parallel | manual) and the pacing question (step_by_step | continuous) are asked in this step, together with the queue. Every user-facing O3 status summary or transition must show the complete table for every PLAN step exactly once, including when no step is eligible or a blocker stops the queue. Never derive the displayed rows from the pending-only dispatch queue. That confirm has no written deadline: follow core/policy/guardrails.md § Open questions without a written deadline. Use the host interactive question when the host offers one; otherwise ask in text. Send no further message until the operator answers every pending question. Silence, timeout, and end of turn are not answers. After the answer, resume this skill until the queued step finishes or this skill declares a blocker with the cause. Read references/execution-modes.md, references/develop-modes.md, references/plan-contract.md, and references/step-queue-spawn.md.
5. Spawn exactly one step child (CA5)
Read references/step-queue-spawn.md § Step 5 - spawn exactly one step child at this step (display ledger, roster spawn conditions, claim lifecycle, receipt reconciliation).
5.5 Post-implement verifier (opt-in)
When preferences.json has verify_mode: true, spawn a read-only verifier child after a successful implementer return and before CONTINUITY update / next spawn. Default verify_mode is false — skip when unset. The verifier uses its separate result contract in references/step-verifier.md; do not validate it as an implementer relay. Read that reference.
6. Safe parallelism (optional)
Default serial mode. Parallel only when mode is parallel and all independence conditions + user confirm + distinct SESSION files; cap ≤4. Mode violations reject/audit — never silent ignore. Read references/execution-modes.md and references/parallelism.md.
7. Stop conditions
Stop on story/feature done, context pressure, child blocked, or cancel. Read references/continuity-handoff.md § Process — Stop conditions.
8. CONTINUITY
Update phase / Memory-bank / estado / handoff at each milestone. Read references/continuity-handoff.md.
9. Step N - Memory Bank refresh-light (after code changes)
When a child changed app files: confirm → refresh-light → CONTINUITY refreshed (or skip). Read references/continuity-handoff.md § Process — Step N refresh-light and references/preconditions.md § Step N - refresh-light.
10. Handoff
Run the scope-close loop only when the operator asked to close the wave. When the operator did not ask, do not start run-tests, code-review, a post-review rerun, the security review, or another specialist the operator did not request. For a requested close, render and maintain the separate O3 closeout table in LIVE-STAGE-TABLE.md alongside the PLAN-step table; update it after each gate result and any later change that affects its evidence.
When the operator asked to close the wave, use this required order: run-tests -> code-review -> run-tests after review changes (or record that no changes required a rerun) -> the security role/prompt review of the diff -> assign an applicable build to shell-runner at US close only -> ask /commit -> ask /push separately. If no build command applies, record not applicable. Do not run build per step. When code review is requested against this PLAN, run the impact, architecture, and persistence pass again before that review (repo-analyst, architect, and database when the PLAN cites persistence). That second pass is not a per-step spawn. Read references/continuity-handoff.md § Handoff copy. The security handoff is role-based ({{TOOLKIT_ROOT}}/skills/_shared/agents/prompts/security.md); use the host’s documented spawn mechanism when available, otherwise perform the bounded fallback in-parent. Do not claim a /security command or host capability that is not present. A requested wave close may still record converge, sync_current, and archive (TRACE-ARCHIVE-CONTRACT.md). Do not delete that contract.
Anti-bypass checklist (must enforce)
Read references/anti-bypass.md before every spawn and before marking any step done; it holds the full CA5 table.
Must not
Enforce the full list in references/must-not.md. Critical always-on: no parent app code; no multi-step children; no hard-fail when Agent unavailable (fallback /sdd-develop); portable paths only; do not ignore IC-DIRECT-ORCHESTRATED (INVOCATION-CONTEXTS.md).
Handoff
| Situation | Next |
|---|---|
| Next PLAN step | New chat -> orchestrate-develop or sdd-develop - <plan> - Step N |
| Story/feature done | run-tests, then code-review, then run-tests after review changes, then the security role/prompt review, then /commit, then /push (references/continuity-handoff.md) |
| Missing PLAN | orchestrate-deliver / sdd-plan |
| Prefer no orchestrator | Manual sdd-develop only |
Canonical strings
/orchestrate-develop - <portable-feature-path>
/sdd-develop - <portable-plan-path> - Step N
/code-review
/code-review - multi-angle