settings
01Settings file Claude Code
Agent settings declaring 4 hook events (PreToolUse, PostToolUse, InstructionsLoaded, Stop).
Settings file Claude Code
Agent settings declaring 4 hook events (PreToolUse, PostToolUse, InstructionsLoaded, Stop).
Instructions file CodexOpenCode
AGENTS.md instructions for esneiderbravo/speclaw, covering agents.md — speclaw, project, mandatory operating rules, the standards (the law, in detail) and directory map for agents.
Instructions file
Claude Code instructions for esneiderbravo/speclaw, covering claude.md — speclaw agent operating rules, rule 0 — the law comes first, rule 1 — compass first, always, rule 2 — spec-driven, always and rule 3 — quality gates are non-negotiable.
Command
Finalize a completed change — sync specs when needed, then archive it.
Command
Implement a drafted change, following its spec and the project's standards.
Command
Draft a new spec-driven change at the confirmed ceremony level before coding.
Command
Enter explore mode — a thinking partner before or during a change.
Command
Investigate a bug — graph-backed suspect ranking before draft --bug.
Command
Scaffold a level-0 lawbook change (record.md + reports) for a tiny fix.
Command
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).
Agent
Use this agent for backend planning, reviews, and refactors in this repository. Focus on the backend source and test trees, migration wiring, and the service/workflow boundaries documented in AGENTS.md and LAWS.md.
Agent
Use this agent for frontend planning, reviews, and refactors in this repository. Focus on the frontend source tree, shared UI, i18n boundaries, and the build/runtime constraints documented in AGENTS.md and LAWS.md.
Agent
Use this agent for product discovery, scope definition, and requirement shaping before implementation in this repository.
MCP server Claude CodeCodexCursor
Where specs become law. A self-contained MCP suite that turns any repo into a spec-driven, agent-ready project: its own constitution (foundation), its own local code graph (Compass), its own spec-driven workflow (Lawbook), and opt-in skill packs (Tools). Runs locally from the @esneiderbravo/speclaw npm package.