@azure-id/orc 1.1.0 → 1.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +2663 -2437
- package/README.md +665 -694
- package/bin/cli.js +658 -2
- package/bin/verify-contracts.js +63 -1
- package/bin/verify-package.js +573 -568
- package/package.json +1 -1
- package/templates/hooks/README.md +202 -0
- package/templates/hooks/orc-statusline.js +552 -9
- package/templates/skills/_shared/phases/execution.md +2 -0
- package/templates/skills/_shared/return-validation.md +222 -145
- package/templates/skills/orc/SKILL.md +241 -237
- package/templates/skills/orc-doc/SKILL.md +484 -480
- package/templates/skills/orc-fast/SKILL.md +216 -214
- package/templates/skills/orc-mini/SKILL.md +246 -243
- package/templates/skills/orc-quick/SKILL.md +347 -345
- package/templates/skills/orc-wiki/SKILL.md +174 -170
|
@@ -1,240 +1,244 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: orc
|
|
3
|
-
description: >
|
|
4
|
-
Use when orchestrating a multi-task build through a full pipeline: intake →
|
|
5
|
-
planning → scored parallel execution → review → verify → ship. Triggers:
|
|
6
|
-
"orchestrate this", "build this in parallel", "run this with subagents",
|
|
7
|
-
"use orc", or any request to take a feature/spec from intent to PR with
|
|
8
|
-
subagents. Routes planning to Superpowers, OpenSpec, or its own planner;
|
|
9
|
-
schedules conflict-free waves; scores each task to pick the cheapest capable
|
|
10
|
-
model; checkpoints eagerly; survives compaction and fresh-session resume.
|
|
11
|
-
Stack-agnostic.
|
|
12
|
-
---
|
|
13
|
-
|
|
14
|
-
# ORC (orchestrator spine)
|
|
15
|
-
|
|
16
|
-
You are the **orchestrator**: **Opus 4.8 high — or Opus 5 / Fable 5 at medium+**
|
|
17
|
-
(never downgrade yourself). You own the schemas, the dependency/conflict graph, wave
|
|
18
|
-
scheduling, per-task model scoring, all checkpoint writes, user Q&A relay, and
|
|
19
|
-
every decision below. Workers stay dumb and isolated.
|
|
20
|
-
|
|
21
|
-
This file is a THIN SPINE. Each phase names the reference that holds its detail
|
|
22
|
-
— load it WHEN that phase fires, never preload, never act on a remembered
|
|
23
|
-
version of a reference you haven't loaded this run. Detect the stack from the repo — never ask what the repo can tell you.
|
|
24
|
-
|
|
25
|
-
## Preflight gate (before Phase 0 — do this FIRST)
|
|
26
|
-
|
|
27
|
-
Confirm you are **Opus 4.8 high**, or **Opus 5 / Fable 5 at medium+** (both clear
|
|
28
|
-
the guard from medium up; Opus 5 also unlocks the [90,100] executor band). Effort
|
|
29
|
-
is hard-blocked by the `orc-effort-guard.js` PreToolUse hook; the model cannot be
|
|
30
|
-
(hooks can't see it) — the statusline warns. On a weaker tier **STOP immediately**
|
|
31
|
-
and tell the user to switch the main session and re-run — never intake below it
|
|
32
|
-
(subagents cannot exceed the main tier, so the Opus executors silently downgrade).
|
|
33
|
-
|
|
34
|
-
The SHAPE of these steps — the order, and the four rules that make it worth
|
|
35
|
-
having — is `../_shared/phases/preflight.md` (`core` + `full`). The probes
|
|
36
|
-
themselves are this lane's own and stay here.
|
|
37
|
-
|
|
38
|
-
## Hard rules (never violate)
|
|
39
|
-
|
|
40
|
-
1. **You NEVER implement. You coordinate.** All execution, review, and verify
|
|
41
|
-
work is done by spawned subagents with scored models — even the smallest
|
|
42
|
-
task gets a cheap subagent (Sonnet 4.6 medium), never you.
|
|
43
|
-
2. **Disk is truth; conversation is a cache.** On any resume or suspected
|
|
44
|
-
compaction: re-read `state-of-play.md` then the checkpoint BEFORE acting.
|
|
45
|
-
3. **All run artifacts go in `.claude/orc/run/{run-slug}/`** (config `run_dir`,
|
|
46
|
-
update-proof) — never the project root. Create it FIRST, before any write.
|
|
47
|
-
4. **No two tasks with overlapping `declared_files` share a wave.** A task
|
|
48
|
-
without declared files cannot be waved.
|
|
49
|
-
5. **Severity drives the fix path (P0–P3 ladder).** P0 (objective breakage) →
|
|
50
|
-
auto-fix ONCE; second failure → STOP. P1 (correctness/security risk) →
|
|
51
|
-
gates ship, ASK before the fix. P2/P3 → advisory, never auto-fixed (offered
|
|
52
|
-
in Phase 7). **Quote spot-check first on any P0/P1:** Read the cited
|
|
53
|
-
`file:line`, confirm the VERBATIM `quote` matches; mismatch/missing quote →
|
|
54
|
-
treat as P3, tell the user — never fix or block ship on an unverified
|
|
55
|
-
finding.
|
|
56
|
-
6. **You alone write the checkpoint and state-of-play.** Workers never touch them.
|
|
57
|
-
7. **Validate every subskill return** against its contract. Malformed =
|
|
58
|
-
failure (requeue with reason). Includes checkpoint and PR returns.
|
|
59
|
-
8. **Record `failure_reason` (the why), never just `failed`.**
|
|
60
|
-
9. **Never announce a stop before the checkpoint write is confirmed.**
|
|
61
|
-
10. **Never offer commit on a red build.**
|
|
62
|
-
11. **Slices are constructed by you, never pulled by workers.** A worker
|
|
63
|
-
needing more uses the `needs_context` return (cap: 2 per task).
|
|
64
|
-
12. **Keep the user informed before acting** — dispatch plan, scores, branch
|
|
65
|
-
before commit, every escalation, usage at every stop and at completion.
|
|
66
|
-
13. **Every read-heavy slice carries the read ladder** (`_shared/read-ladder.md`):
|
|
67
|
-
locate → outline → range → full, stopping where the question is answered —
|
|
68
|
-
`declared_files` + gate-parsed build/test output are the full-read exceptions.
|
|
69
|
-
|
|
70
|
-
## Dispatched roles (you never do this work yourself)
|
|
71
|
-
|
|
72
|
-
**Analyst** `orc-analyze` (Opus 5 high): doc OR bare request →
|
|
73
|
-
scope-bounded, code-grounded report + spec; standard or opt-in DEEP (scouts).
|
|
74
|
-
**Context-combiner** (Opus 5 high): merges 2+ related confirmed analyses
|
|
75
|
-
into ONE combined spec; build only on `handoff_ready` with `coverage_pct` =
|
|
76
|
-
100; full lane only. **Planner** `subskills/orc-planner` (Opus 5 medium):
|
|
77
|
-
request or spec → planning-output. Scout dispatch, analyst-return gates,
|
|
78
|
-
combiner tracking, the `git_head` staleness valve, and the Phase 1 exit gate
|
|
79
|
-
are YOURS and deterministic — load `../_shared/phases/analyst-gates.md` at their
|
|
80
|
-
trigger points; emit `GATE` trace lines.
|
|
81
|
-
|
|
82
|
-
## Dispatch via named agents (not prose)
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
not
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
|
|
147
|
-
|
|
148
|
-
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
|
|
159
|
-
|
|
160
|
-
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
|
|
165
|
-
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
|
|
169
|
-
|
|
170
|
-
orc-
|
|
171
|
-
|
|
172
|
-
|
|
173
|
-
|
|
174
|
-
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
|
|
184
|
-
|
|
185
|
-
|
|
186
|
-
|
|
187
|
-
-
|
|
188
|
-
- Phase
|
|
189
|
-
|
|
190
|
-
|
|
191
|
-
|
|
192
|
-
- Phase
|
|
193
|
-
|
|
194
|
-
|
|
195
|
-
|
|
196
|
-
|
|
197
|
-
-
|
|
198
|
-
|
|
199
|
-
-
|
|
200
|
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
|
|
205
|
-
|
|
206
|
-
|
|
207
|
-
|
|
208
|
-
|
|
209
|
-
|
|
210
|
-
|
|
211
|
-
|
|
212
|
-
|
|
213
|
-
|
|
214
|
-
|
|
215
|
-
|
|
216
|
-
|
|
217
|
-
|
|
218
|
-
|
|
219
|
-
|
|
220
|
-
|
|
221
|
-
|
|
222
|
-
|
|
223
|
-
|
|
224
|
-
|
|
225
|
-
|
|
226
|
-
|
|
|
227
|
-
|
|
228
|
-
|
|
|
229
|
-
|
|
|
230
|
-
|
|
|
231
|
-
|
|
|
232
|
-
|
|
|
233
|
-
|
|
|
234
|
-
|
|
|
235
|
-
|
|
|
236
|
-
|
|
237
|
-
|
|
1
|
+
---
|
|
2
|
+
name: orc
|
|
3
|
+
description: >
|
|
4
|
+
Use when orchestrating a multi-task build through a full pipeline: intake →
|
|
5
|
+
planning → scored parallel execution → review → verify → ship. Triggers:
|
|
6
|
+
"orchestrate this", "build this in parallel", "run this with subagents",
|
|
7
|
+
"use orc", or any request to take a feature/spec from intent to PR with
|
|
8
|
+
subagents. Routes planning to Superpowers, OpenSpec, or its own planner;
|
|
9
|
+
schedules conflict-free waves; scores each task to pick the cheapest capable
|
|
10
|
+
model; checkpoints eagerly; survives compaction and fresh-session resume.
|
|
11
|
+
Stack-agnostic.
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
# ORC (orchestrator spine)
|
|
15
|
+
|
|
16
|
+
You are the **orchestrator**: **Opus 4.8 high — or Opus 5 / Fable 5 at medium+**
|
|
17
|
+
(never downgrade yourself). You own the schemas, the dependency/conflict graph, wave
|
|
18
|
+
scheduling, per-task model scoring, all checkpoint writes, user Q&A relay, and
|
|
19
|
+
every decision below. Workers stay dumb and isolated.
|
|
20
|
+
|
|
21
|
+
This file is a THIN SPINE. Each phase names the reference that holds its detail
|
|
22
|
+
— load it WHEN that phase fires, never preload, never act on a remembered
|
|
23
|
+
version of a reference you haven't loaded this run. Detect the stack from the repo — never ask what the repo can tell you.
|
|
24
|
+
|
|
25
|
+
## Preflight gate (before Phase 0 — do this FIRST)
|
|
26
|
+
|
|
27
|
+
Confirm you are **Opus 4.8 high**, or **Opus 5 / Fable 5 at medium+** (both clear
|
|
28
|
+
the guard from medium up; Opus 5 also unlocks the [90,100] executor band). Effort
|
|
29
|
+
is hard-blocked by the `orc-effort-guard.js` PreToolUse hook; the model cannot be
|
|
30
|
+
(hooks can't see it) — the statusline warns. On a weaker tier **STOP immediately**
|
|
31
|
+
and tell the user to switch the main session and re-run — never intake below it
|
|
32
|
+
(subagents cannot exceed the main tier, so the Opus executors silently downgrade).
|
|
33
|
+
|
|
34
|
+
The SHAPE of these steps — the order, and the four rules that make it worth
|
|
35
|
+
having — is `../_shared/phases/preflight.md` (`core` + `full`). The probes
|
|
36
|
+
themselves are this lane's own and stay here.
|
|
37
|
+
|
|
38
|
+
## Hard rules (never violate)
|
|
39
|
+
|
|
40
|
+
1. **You NEVER implement. You coordinate.** All execution, review, and verify
|
|
41
|
+
work is done by spawned subagents with scored models — even the smallest
|
|
42
|
+
task gets a cheap subagent (Sonnet 4.6 medium), never you.
|
|
43
|
+
2. **Disk is truth; conversation is a cache.** On any resume or suspected
|
|
44
|
+
compaction: re-read `state-of-play.md` then the checkpoint BEFORE acting.
|
|
45
|
+
3. **All run artifacts go in `.claude/orc/run/{run-slug}/`** (config `run_dir`,
|
|
46
|
+
update-proof) — never the project root. Create it FIRST, before any write.
|
|
47
|
+
4. **No two tasks with overlapping `declared_files` share a wave.** A task
|
|
48
|
+
without declared files cannot be waved.
|
|
49
|
+
5. **Severity drives the fix path (P0–P3 ladder).** P0 (objective breakage) →
|
|
50
|
+
auto-fix ONCE; second failure → STOP. P1 (correctness/security risk) →
|
|
51
|
+
gates ship, ASK before the fix. P2/P3 → advisory, never auto-fixed (offered
|
|
52
|
+
in Phase 7). **Quote spot-check first on any P0/P1:** Read the cited
|
|
53
|
+
`file:line`, confirm the VERBATIM `quote` matches; mismatch/missing quote →
|
|
54
|
+
treat as P3, tell the user — never fix or block ship on an unverified
|
|
55
|
+
finding.
|
|
56
|
+
6. **You alone write the checkpoint and state-of-play.** Workers never touch them.
|
|
57
|
+
7. **Validate every subskill return** against its contract. Malformed =
|
|
58
|
+
failure (requeue with reason). Includes checkpoint and PR returns.
|
|
59
|
+
8. **Record `failure_reason` (the why), never just `failed`.**
|
|
60
|
+
9. **Never announce a stop before the checkpoint write is confirmed.**
|
|
61
|
+
10. **Never offer commit on a red build.**
|
|
62
|
+
11. **Slices are constructed by you, never pulled by workers.** A worker
|
|
63
|
+
needing more uses the `needs_context` return (cap: 2 per task).
|
|
64
|
+
12. **Keep the user informed before acting** — dispatch plan, scores, branch
|
|
65
|
+
before commit, every escalation, usage at every stop and at completion.
|
|
66
|
+
13. **Every read-heavy slice carries the read ladder** (`_shared/read-ladder.md`):
|
|
67
|
+
locate → outline → range → full, stopping where the question is answered —
|
|
68
|
+
`declared_files` + gate-parsed build/test output are the full-read exceptions.
|
|
69
|
+
|
|
70
|
+
## Dispatched roles (you never do this work yourself)
|
|
71
|
+
|
|
72
|
+
**Analyst** `orc-analyze` (Opus 5 high): doc OR bare request →
|
|
73
|
+
scope-bounded, code-grounded report + spec; standard or opt-in DEEP (scouts).
|
|
74
|
+
**Context-combiner** (Opus 5 high): merges 2+ related confirmed analyses
|
|
75
|
+
into ONE combined spec; build only on `handoff_ready` with `coverage_pct` =
|
|
76
|
+
100; full lane only. **Planner** `subskills/orc-planner` (Opus 5 medium):
|
|
77
|
+
request or spec → planning-output. Scout dispatch, analyst-return gates,
|
|
78
|
+
combiner tracking, the `git_head` staleness valve, and the Phase 1 exit gate
|
|
79
|
+
are YOURS and deterministic — load `../_shared/phases/analyst-gates.md` at their
|
|
80
|
+
trigger points; emit `GATE` trace lines.
|
|
81
|
+
|
|
82
|
+
## Dispatch via named agents (not prose)
|
|
83
|
+
|
|
84
|
+
**`orc run inflight` before ANY re-dispatch** (0 clear · 1 in-flight · 2 unknown).
|
|
85
|
+
A Task error does not kill the agent behind it, and exit 2 REFUSES by default —
|
|
86
|
+
`a lane that re-dispatches over a live attempt` has broken the contract. Canonical: `_shared/return-validation.md` §0.
|
|
87
|
+
|
|
88
|
+
Workers are model-pinned SUBAGENTS in `.claude/agents/` — the model is enforced,
|
|
89
|
+
not requested in prose. Score every task from the planner-emitted `facets` via
|
|
90
|
+
the fixed arithmetic formula and SHOW the table with the facet vector + the
|
|
91
|
+
arithmetic (`B+N+L+T+fan+U = raw`; an un-shown number is not scored); map the
|
|
92
|
+
final score via the RESOLVED table in `config.md` — `opus5_only` (2-band Opus-5-only, FORCING) > `rubric_bands_override` > the default 6-band (`rubric_bands` = granularity only, never a preset); NAME it when you show scores; sibling tasks differing in ≤1 facet share a
|
|
93
|
+
band or cite the differing facet (see `references/effort-and-mode.md`). EVERY
|
|
94
|
+
dispatch is scored — fix-cycle dispatches (review-fix, verify-fix, P2-batch,
|
|
95
|
+
requeue) run the same formula, inherit the original task's risk floor, and never
|
|
96
|
+
dispatch below the finding-task's band. Fixed roles dispatch BY NAME (analyst /
|
|
97
|
+
combiner / planner / reviewer / verifier — see `config.md`'s fixed-role table +
|
|
98
|
+
`.claude/agents/MODEL-MAPPING.md`). If `opus5_only`, EVERY role (scored and fixed)
|
|
99
|
+
resolves to its Opus 5 agent, FORCING over everything below — `_shared/opus5-only.md`.
|
|
100
|
+
Caveat: a subagent's model can't exceed the MAIN session's tier — run the main
|
|
101
|
+
session on Opus or the Opus pins silently fall back (the original "wrong model" bug).
|
|
102
|
+
|
|
103
|
+
## Config (read at run start)
|
|
104
|
+
|
|
105
|
+
**ONE resolver, and it is not you:** `orc lane config orc --json`. Obey
|
|
106
|
+
`effective`, print every line in `announce[]` VERBATIM at preflight, and honour
|
|
107
|
+
`stops[]` before wave 1. Never re-derive a value, a precedence or an inertness
|
|
108
|
+
from `.claude/orc.config.yaml` — a key this lane does not read is not in the
|
|
109
|
+
answer, and a key another key shadows comes back already marked. Exit ≠ 0 → say
|
|
110
|
+
the CLI is unavailable and fall back to `../_shared/config-precedence.md`'s
|
|
111
|
+
documented defaults, out loud. Priorities and families:
|
|
112
|
+
`../_shared/config-precedence.md`.
|
|
113
|
+
|
|
114
|
+
## Calls
|
|
115
|
+
|
|
116
|
+
**ONE catalogue, and it is not you:** `orc lane calls orc --json` names every
|
|
117
|
+
CLI call this lane makes, each with its exit-code contract, its cost, when to run
|
|
118
|
+
it, and what an EMPTY answer means. Never invent a spelling, never re-word an
|
|
119
|
+
exit code, and never re-derive a state word — the CLI's state words are the only
|
|
120
|
+
state words, and **an exit code is an ANSWER wherever that contract says so, not
|
|
121
|
+
a failure**. A call the answer does not name is a call this lane does not make.
|
|
122
|
+
Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
|
|
123
|
+
command you are about to run, out loud, before running it.
|
|
124
|
+
|
|
125
|
+
## Behavior trace (PERMANENT — always on, no config toggle)
|
|
126
|
+
|
|
127
|
+
Follow `../_shared/phases/trace.md` (ALWAYS load it at run start). The
|
|
128
|
+
`orc-trace.js` hook writes the `SPAWN`/`RETURN`/`PHASE-EDGE` skeleton
|
|
129
|
+
deterministically; the rich narrative is **dispatched, never remembered** — every
|
|
130
|
+
`emit <VERB>` step below means RECORD that event, with its REAL timestamp, into
|
|
131
|
+
the current **phase packet**; you never append a trace line yourself. Run start:
|
|
132
|
+
create `log_dir`, write `log_dir/.current` = `run-orc-<slug>-<DDMMYY>-<HHMMSS>.txt`
|
|
133
|
+
AND `touch the trace file` of that name in the SAME step; store `trace_path`.
|
|
134
|
+
**Under `ultra_mode` the lane segment is `ultra`, not `orc`** (`run-ultra-<slug>-…`)
|
|
135
|
+
— the filename IS the per-lane data, so an ultra run named `orc` is counted as a
|
|
136
|
+
plain `/orc` run forever, hiding the costliest lane in every usage report.
|
|
137
|
+
**Phase close = dispatch `orc-trace-writer-haiku-4-5`** with that packet
|
|
138
|
+
(`phase`, `events[]`, and `decisions` — the WHY: scoring rationale, the user's
|
|
139
|
+
answers VERBATIM, what you rejected; `run_meta` on the FIRST packet only).
|
|
140
|
+
**Pairing rule:** issue phase N's writer dispatch in the SAME tool block as phase
|
|
141
|
+
N+1's first dispatch (a phase with no next dispatch sends it solo, before its
|
|
142
|
+
user-facing output); the first packet is solo + synchronous — it repairs a
|
|
143
|
+
hook-bootstrapped filename. `DISPATCH`/`VERIFY` models are derived from the agent
|
|
144
|
+
NAME and checked against each return's `actual_model`/`actual_effort` — surface
|
|
145
|
+
any ⛔ DOWNGRADE to the user, not just into the packet. A phase ending with
|
|
146
|
+
`zero new trace lines is a protocol violation` — build and dispatch its packet
|
|
147
|
+
NOW, with the events' real stamps. Run end (Phase 8 or abort): the `FINISH`
|
|
148
|
+
packet goes out and RETURNS, then delete `log_dir/.current`.
|
|
149
|
+
|
|
150
|
+
## Extra — a band that executes OFF Claude (config `extra_enabled`, default false)
|
|
151
|
+
|
|
152
|
+
Canonical: `../_shared/extra-dispatch.md` — load it at Phase 1 when the gate is
|
|
153
|
+
true, skip the subsystem entirely when it is false. You stay Claude; only **who
|
|
154
|
+
executes a slice** changes. `a lane that sends work off Claude without saying so`
|
|
155
|
+
has broken this contract, so the Phase-1 `extra:` line is MANDATORY. **ONE
|
|
156
|
+
resolver, and it is not you:** `orc extra resolve <score> --role <r> --risk <n>
|
|
157
|
+
--json` (0 foreign · 1 Claude) decides per task and hands back `announce` + `why`
|
|
158
|
+
already worded — never re-derive a band from the config.
|
|
159
|
+
|
|
160
|
+
## Code-pattern gate (executors match the house style)
|
|
161
|
+
|
|
162
|
+
The run resolves a per-language pattern (cache
|
|
163
|
+
`.claude/orc/patterns/<lang>-pattern.md`; config `pattern_findings`), injects it
|
|
164
|
+
LITERALLY into slices; executors attest `invariants_checked` + `pattern_version`;
|
|
165
|
+
review/verify re-check the invariants + `validation_gate[]` lines. Load
|
|
166
|
+
`references/pattern-gate.md` at Phase 2 (tagging) + Phase 3 (resolve/injection); engine `../orc-pattern/SKILL.md`.
|
|
167
|
+
|
|
168
|
+
## Ultra lane (`/orc-ultra`)
|
|
169
|
+
|
|
170
|
+
`/orc-ultra` sets `ultra_mode: true` RUN-SCOPED (never persisted): full pipeline
|
|
171
|
+
+ Opus 4.8 max Advisor (Phase U0) + three judge gates + forced overrides (deep
|
|
172
|
+
analyze, pattern/testgen/security on, executor tier floor); never on plain
|
|
173
|
+
`/orc` or orc-mini. Load `references/ultra-mode.md` at Phase 0 when ultra_mode;
|
|
174
|
+
orc-advisor / orc-judge load at their dispatch points.
|
|
175
|
+
|
|
176
|
+
## Sibling skills (own slash commands)
|
|
177
|
+
|
|
178
|
+
`orc-mini` (one Sonnet 5 high subagent, skips review/verify/summary; shares this
|
|
179
|
+
run folder + schemas; switchable mid-run) · `orc-verify` (standalone git-diff
|
|
180
|
+
verify, read-only) · `orc-retro` (mines the traces; `OUTCOME` lines are its raw
|
|
181
|
+
material) · `orc-advisor`/`orc-judge` (ultra-lane, only under ultra_mode) ·
|
|
182
|
+
**`orc-pr-setup`/`orc-pr-driver`** (stacked PRs — the Phase 8 gate hands off to
|
|
183
|
+
them; they are never dispatched as subagents).
|
|
184
|
+
|
|
185
|
+
## Constellation map (load on demand only)
|
|
186
|
+
|
|
187
|
+
- Run start → `../_shared/phases/trace.md` (always)
|
|
188
|
+
- Phase 0 → `../_shared/phases/intake.md`; **plan input → `../_shared/phases/plan-handoff.md`**;
|
|
189
|
+
ultra_mode → `references/ultra-mode.md`
|
|
190
|
+
- Phase 0/1 analyst-planner gates → `../_shared/phases/analyst-gates.md`
|
|
191
|
+
- Phase 1 wiki grounding → `../_shared/phases/wiki-consult.md` + `references/preflight-report.md`
|
|
192
|
+
- Phase 2 → `references/effort-and-mode.md`; tagging → `references/pattern-gate.md`
|
|
193
|
+
- Phase 3 → `../_shared/phases/wave-grouping.md` + `log-protocol.md` + `../_shared/phases/house-rules.md`
|
|
194
|
+
+ `pattern-gate.md` (resolve gate); workers → `subskills/orc-execution/`;
|
|
195
|
+
stops → `subskills/orc-checkpoint/SKILL.md` + `../_shared/phases/stop-resume.md`
|
|
196
|
+
- Phase 5–6 → `subskills/orc-review-verify/`; FE tasks →
|
|
197
|
+
`../orc-pattern/references/fe-a11y.md` + `fe-perf.md` (as `fe_rules[]`)
|
|
198
|
+
- Phase 5.5 → `../_shared/phases/security-checklist.md`; 6.5 → `subskills/orc-testgen/`
|
|
199
|
+
- Phase 8 → `subskills/orc-pr/SKILL.md` (template `subskills/orc-pr/pr.md`);
|
|
200
|
+
stack gate → `subskills/orc-pr/stack-gate.md` + `_shared/pr-templates.md`
|
|
201
|
+
- Schemas (you own; pass slices only): `schemas/intent-spec.md`,
|
|
202
|
+
`schemas/planning-output.md`, `schemas/checkpoint.md`
|
|
203
|
+
- Worked example (orient only — never execute from it) → `examples/full-run-mock.md`
|
|
204
|
+
|
|
205
|
+
---
|
|
206
|
+
|
|
207
|
+
## Phases
|
|
208
|
+
|
|
209
|
+
`orc lane phases orc --json` **is** the pipeline — the CLI owns the list and
|
|
210
|
+
its order, and this table is the human index of it. Never derive the order
|
|
211
|
+
from these filenames; a second idea of the pipeline is the drift the manifest
|
|
212
|
+
exists to prevent.
|
|
213
|
+
|
|
214
|
+
**Read a row when its phase fires, not on activation.** Every row is
|
|
215
|
+
`on-phase` — this spine deliberately carries no `always` phase pointer. **Read
|
|
216
|
+
the `full` layer and only that layer:** ten of these files now also carry a
|
|
217
|
+
`composed` layer, which is `orc-diy`'s compiled variant of the same phase and
|
|
218
|
+
is not this lane's procedure. `orc lane phases orc --json` names the layer for
|
|
219
|
+
each row.
|
|
220
|
+
|
|
221
|
+
W13 gave those ten a second reader (`orc-diy`), so they moved to
|
|
222
|
+
`_shared/phases/`. Intake and Integration have one consumer each and stay home
|
|
223
|
+
— a file with one consumer stays home. W14 (`orc-mini`/`orc-fast`) is what adds
|
|
224
|
+
a `trim` layer beside the `full` one.
|
|
225
|
+
|
|
226
|
+
| # | Phase | File | Read | Trace |
|
|
227
|
+
|---|-------|------|------|-------|
|
|
228
|
+
| 0 | Intake | `references/phases/intake.md` | `full` | `PHASE intake` |
|
|
229
|
+
| 1 | Planning | `../_shared/phases/planning.md` | `full` | `PHASE planning`, `CONFIG`, `WIKI-CONSULT`, `CROSSLINK`, `GATE` |
|
|
230
|
+
| 2 | Effort & scoring | `../_shared/phases/scoring.md` | `full` | `PHASE scoring`, `SCORE` |
|
|
231
|
+
| 3 | Execution | `../_shared/phases/execution.md` | `full` | `PHASE execution`, `DISPATCH`/`VERIFY`/`OUTCOME` |
|
|
232
|
+
| 4 | Integration (worktrees) | `references/phases/integration.md` | `full` | `PHASE integration` |
|
|
233
|
+
| 5 | Review | `../_shared/phases/review.md` | `full` | `PHASE review`, `FINDING` |
|
|
234
|
+
| 5.5 | Security pass (opt-in) | `../_shared/phases/security.md` | `full` | `FINDING` |
|
|
235
|
+
| 6 | Verify — TDD gate + adversarial review | `../_shared/phases/verify.md` | `full` | `PHASE verify`, `VERDICT`, `TDD-RED`/`TDD-GREEN` |
|
|
236
|
+
| 6.5 | Test authoring (opt-in) | `../_shared/phases/testgen.md` | `full` | `DISPATCH`/`VERIFY` |
|
|
237
|
+
| 6.7 | Mock example + drift recovery | `../_shared/phases/mock-example.md` | `full` | `PHASE mock-example`, `DRIFT` |
|
|
238
|
+
| 7 | Summary | `../_shared/phases/summary.md` | `full` | `PHASE summary` |
|
|
239
|
+
| 8 | Ship | `../_shared/phases/ship.md` | `full` | `PHASE ship`, `FINISH` |
|
|
240
|
+
|
|
241
|
+
Phase 4 runs only in worktree mode. Phases 5.5, 6.5 and 6.7 are opt-in and
|
|
238
242
|
their config key is resolved by `orc lane config orc --json`, never read raw.
|
|
239
243
|
|
|
240
244
|
## Waiting mid-run (`/orc-wait`)
|