scottcrosby-securebine/doctrine
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.
Use when the user asks to back up the session, save session memory, update SESSION_MEMORY.md, or wrap up so the next session can pick up where this one left off. Writes the repo's memory file as survivable session context and red-teams it before reporting done.
Use when the user asks for a handoff document, "a detailed backup and a handoff so I can clear the session", or anything that carries this session's detail to the next cleared session. Writes a new file under docs/handoffs/ tied to the plan, then runs doctrine-backup so the memory file points at it and both are red-teamed.
Use when the user asks you to pop a pane, ssh into a box, log into a router or switch, get onto a console, or tail or monitor a log while you work — any interactive terminal session they want to watch live and be able to take over. Not for automated work, which stays on its MCP server or a plain command.
Use when starting cold in a repo, when the user asks to prime, orient, or get a situation report, or when an agent has never seen this repo. Restores session state exactly as doctrine-resume does, then explains the project.
Use when the user asks to load memory, resume the session, restore state, or pick up where the last session left off. Reads SESSION_MEMORY.md and the handoff its kickoff names, loads the doctrine when a doctrine phase is open, and reports drift. State only, no codebase tour.