doctrine-orchestrate
Pinned to revision 971a02fd4fda, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.
An execution posture for substantial agent work: parallel agents in phases and waves, adversarial red-teaming, looping until confident, ruthless simplicity. Fifteen skills: a shared doctrine, wrappers for coding, web design (the gauntlet loop), debugging, auditing, documentation sweeps, deep research, document writing, project and epic tracking (doctrine-project), and orchestrated runs of several phases at once, each in its own lane session, landed one at a time behind a gate (doctrine-orchestrate), plus doctrine-backup, doctrine-handoff, doctrine-resume and doctrine-primer for session continuity across cleared sessions, and doctrine-pane for an interactive terminal session in a pane the user watches and can take over. Composes with (and degrades gracefully without) Matt Pocock's engineering skills, superpowers, codex, ponytail, and Claude Design. Three skills need something installed, and each refuses rather than falling back to a weaker version of themselves: doctrine-gauntlet needs Playwright, because its critics judge rendered output — without a browser its harness refuses to run rather than report a pass — doctrine-pane needs herdr, because an interactive session nobody can watch has no purpose, and doctrine-orchestrate needs herdr and Claude Code, because every session of a run lives in a herdr pane. The other twelve skills need nothing installed.
Pinned to revision 971a02fd4fda, so it is the text this page describes rather than whatever the author pushed since.
Every link opens the file at its source, pinned to the revision this page describes.