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

os-sdlc: /implement is a skill-as-orchestrator over the agent pipeline 

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VgG2g9ooqbnBiZYGAonGYG
This commit is contained in:
jared 2026-07-16 16:23:45 -04:00
parent 5c18ba696f
commit 23fa2fbdbd
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
plugins/os-sdlc/reference/pipeline-stages.md
View File

@ -64,8 +64,11 @@ per-example granularity was a DeltaRefinery downside being deliberately dropped.
cc-os naming convention before anything ships.
- Whether a cheap tests-vs-spec review should run *before* the programmer stage in later
versions, to catch misaligned tests before paying for implementation.
- Whether Pocock's `implement` skill is adopted as a thin router over these stages, or
redesigned from scratch.
- Shape settled 2026-07-16: `/implement` (or our custom successor) is a *skill acting as
orchestrator* — slash commands are the user-invocable layer, agents aren't. The skill
triggers the agent pipeline, watches over it, adjusts to surprises, and keeps the user
in the loop on progress/results. Remaining question: how much of Pocock's `implement`
wording survives vs. a from-scratch orchestrator prompt.
## Sources