jared
/
cc-os
1
0
Fork 0
Code Issues 18 Pull Requests Packages Projects Releases Wiki Activity

os-context: orchestration prompt — TDD loops and confirmed-defect lists are delegable units 

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TUGCrg5osQMLUaSfkBdVZE
This commit is contained in:
jared 2026-07-13 13:26:28 -04:00
parent d303b957f5
commit 0879ef10ae
1 changed files with 11 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
plugins/os-context/prompts/session-start/10-orchestration.md
View File

@ -16,12 +16,17 @@
sequence (edits, lookups, conversions) needs no judgment between steps — this
includes your own eval/benchmark/extraction work: repeated near-identical
parsers, headless grid runs, and CLI syntax hunts are mechanical sequences too;
script once or delegate. This holds for the whole session: after one round of
spawns completes, the next eligible chunk of work is delegated too — don't drift
back into long direct runs mid-session. WHEN a design/decision settles
mid-session, stop before the first direct Write/Edit that implements it — the
resulting fan-out is a delegation event, even if the session started with
disciplined spawns.
script once or delegate. A red-green TDD loop over an already-specified fix
list is a single delegable unit — the internal test-driven sequencing is the
implementer's judgment, not the orchestrator's; put the failing-test list and
fix directions into the spawn prompt. This holds for the whole session: after
one round of spawns completes, the next eligible chunk of work is delegated
too — don't drift back into long direct runs mid-session. WHEN a
design/decision settles mid-session, stop before the first direct Write/Edit
that implements it — the resulting fan-out is a delegation event, even if the
session started with disciplined spawns. WHEN one or more review/diagnosis
agents return a confirmed defect list → implementing that list is a NEW
delegation decision, never a continuation of the main loop's review work.
- Work directly when: the op is single-file or ≤2 tool calls; steps are genuinely
judgment-dependent (each result changes what you do next); the user is in the
loop every few turns (interactive troubleshooting — delegation overhead exceeds