archive
01Command Claude Code
Finalize a completed change — sync specs when needed, then archive it.
Command Claude Code
Finalize a completed change — sync specs when needed, then archive it.
Command Claude Code
Implement a drafted change, following its spec and the project's standards.
Command Claude Code
Draft a new spec-driven change at the confirmed ceremony level before coding.
Command Claude Code
Enter explore mode — a thinking partner before or during a change.
Command Claude Code
Investigate a bug — graph-backed suspect ranking before draft --bug.
Command Claude Code
Scaffold a level-0 lawbook change (record.md + reports) for a tiny fix.
Command Claude Code
Promote a change's delta specs into the canonical specs, without archiving.
Skill Claude CodeCodex
Finalize a completed change — sync its specs into canonical, then move it to the archive. Use when a change is done and merged-ready: "archive the change", "finalize X", "close out the change". Part of speclaw's lawbook module (draft → build → sync → archive). Archiving belongs in the same PR that implements the…
Skill Claude CodeCodex
Draft a new spec-driven change — propose a ceremony level, then write only the artifacts that level needs — before writing any code. Use when the user wants to start, plan, or propose a new feature, fix, or refactor: "draft a change for X", "propose X", "let's plan X", "spec out X", "new change". Part of speclaw's…
Skill Claude CodeCodex
Enter explore mode — a thinking partner for investigating an idea, a problem, or the codebase before or during a change. Use when the user wants to think something through, understand how something works, or clarify requirements before committing to a spec: "help me think through X", "how does X work", "explore X"…
Skill Claude CodeCodex
Forensic bug triage — rank suspects via lawbookinvestigate before draft --bug. Use with a stack trace or symptom when starting RCA.
Skill Claude CodeCodex
Scaffold a level-0 lawbook change (record.md + reports) for a tiny fix. Use when the user wants a one-line fix, typo, or docs-only tweak without full ceremony — "quick change", "speclaw quick", "level 0", "skip proposal".
Skill Claude CodeCodex
Promote a change's delta specs into the canonical specs, without archiving. Use when the user wants to update the source-of-truth specs from a change: "sync the specs", "update the canonical specs", "promote the specs". Part of speclaw's lawbook module (draft → build → sync → archive).
MCP server Claude CodeCodexCursor +2
Where specs become law. A self-contained MCP suite that turns any repo into a spec-driven, multi-agent-ready project: its own constitution (Foundation), local code graph (Compass), spec workflow (Lawbook), and multi-agent brain (Cortex). No external CLIs. Runs locally from the @esneiderbravo/speclaw npm package.
Agent Claude Code
Reconcile specs, sync, and archive a change when Cortex stage is archiving. No new feature implementation.
Agent Claude Code
Read-only codebase investigation for a lawbook change. Use when the Cortex stage is exploring (or investigate for bugs). Compass-first; writes nothing under lawbook/ or src/.
Agent Claude Code
Implement drafted lawbook tasks in source and tests. Use when Cortex stage is implementing. Does not run final quality gates, review, sync, or archive.
Agent Claude Code
Draft lawbook change artifacts and ceremony level. Use when Cortex stage is planning. Asks clarifying questions via the coordinator; never edits src/.
Agent Claude Code
Scoped review of an implemented change — diff first, defect checklist, short reports/review.md with PASS or FAIL. Never patches code. Use when Cortex stage is reviewing.
Agent Claude Code
Run quality gates and manual verification; write discipline reports. Use when Cortex stage is testing. May add missing tests only — not features.
Command Claude Code
Coordinate Cortex (One brain. Many agents.) for a lawbook change until archive.
Skill Claude CodeCodex
Cortex — One brain. Many agents. The standard way to build any change, as fast as one agent: Compass + laws as guardrails, evidence shipped by hook, extra agents only in parallel.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: