Menu
Full execution protocol for MODE: RESUME -- continuing an existing approved plan safely from current state.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
End-to-end CI monitor that takes an already-human-reviewed PR, exhaustively researches every CI failure, fixes it end-to-end, iterates until all required checks are green (max 5 fix cycles), then merges. Use only after human review is complete and the PR is approved. Composes ci-fix-monitor for failure-type-specific fix recipes. This is the first skill in the repo that executes a merge — invoke it deliberately.
Execute complex implementation work with a swarm-like workflow: parallel exploration, scoped planning, objective validation, mandatory independent implementation review for changed work, and final critic approval. Use for feature work, bug fixes, refactors, and multi-file changes.
Monitor a pull request after creation and act autonomously on pushed PR activity. Use when subscribing to a PR after opening it, when asked to watch, babysit, or autofix a PR until merge, or when a <pr-activity> wake message or [pr-monitor:...] advisory arrives for a subscribed PR. Owns event triage (fix / ask / skip), bounded-retry escalation, and terminal-state cleanup.
Cross-agent swarm-mode behavior model — a higher-rigor workflow using parallel investigation, independent reviewer validation, and critic challenge, plus the mandatory implementation closeout gate. Runtime adapters (.claude, .agents) add execution-specific notes and command wiring.
Full execution protocol for MODE: BRAINSTORM -- structured discovery dialogue, approach selection, spec drafting, QA gate selection, and transition handling.
Full execution protocol for MODE: CLARIFY-SPEC -- resolving spec clarification markers and maintaining spec/planning alignment.
| name | resume |
| description | Full execution protocol for MODE: RESUME -- continuing an existing approved plan safely from current state. |
This protocol is loaded on demand by the architect stub in src/agents/architect.ts. The architect prompt keeps only activation, action, and hard safety constraints; the full execution details live here.
If .swarm/plan.md exists:
.swarm-worktrees/ lane directories and swarm-lane/* git branches left from the prior session. Use the existing cleanupOrphanedBranches / startupOrphanRecovery helpers (or /swarm reset-session recovery) as the mechanism so the resumed run starts from a clean provisioning state..swarm-worktrees/ lane directories and swarm-lane/* git branches left from the prior session. Use the existing cleanupOrphanedBranches / startupOrphanRecovery helpers (or /swarm reset-session recovery) as the mechanism so the resumed run starts from a clean provisioning state.complexity_hotspots tool (90 days) to generate a risk map. Note modules with recommendation "security_review" or "full_gates" in context.md for stricter QA gates during Phase 5. Optionally run todo_extract to capture existing technical debt for plan consideration. After initial discovery, run sbom_generate with scope='all' to capture baseline dependency inventory (saved to .swarm/evidence/sbom/).