romerma

romerma/mstack

Plugin Claude Code

The mstack plugin: rigorous agent workflows with gates that actually gate.

romerma/mstack

Plugin Claude Code

Rigorous, verifiable agent workflows for Claude Code. A router over playbooks, an opt-in spec path, durable state on disk, and gates that are code rather than prose.

romerma/mstack

Instructions file

Claude Code instructions for romerma/mstack, covering mstack, workflow and development.

romerma/mstack

Agent

Implements exactly one mstack work item, writes the tests that prove it, and records the requirement-to-test map. Never marks its own work approved or done.

romerma/mstack

Agent

Owns one work item from intake to close. Selects the next role, enforces the lifecycle, and monitors every launched agent to a terminal result. Never writes application code and never approves its own work.

romerma/mstack

Agent

Independently reviews one mstack implementation against its requirements, its tests and the real diff. Runs the verification itself. Returns APPROVED or CHANGESREQUESTED and never edits the code.

romerma/mstack

Agent

Writes the spec for one item under the mstack spec path. Produces proposal, design, tasks and requirements with stable R-ids, then hands off. Never reviews its own spec.

romerma/mstack

Agent

Reviews one mstack spec independently and adversarially before any code is written. Returns APPROVED or CHANGESREQUESTED. Never edits the spec and never reviews a spec it wrote.

romerma/mstack

Hook

Runs when a session starts, running an inline shell check. From romerma/mstack.

romerma/mstack

Hook

Runs after a tool call finishes for Edit and Write tool calls, running an inline shell check. From romerma/mstack.

romerma/mstack

Hook

Runs when a subagent finishes, running an inline shell check. From romerma/mstack.

romerma/mstack

Hook

Runs when the agent finishes a response, running an inline shell check. From romerma/mstack.

romerma/mstack

Hook

Runs before the agent uses a tool for Bash tool calls, running an inline shell check. From romerma/mstack.

romerma/mstack

Skill Claude CodeCodex

Write commit messages that hold to Conventional Commits 1.0.0, with the type the change actually earns and a description a stranger can read from the log alone. Use before every git commit, when amending or rewording one, when squashing, and when writing a PR title.

romerma/mstack

Skill Claude CodeCodex

Design the shape of a change before writing it, by generating structurally distinct candidates, judging them against criteria fixed in advance, and recording the decision with its rejected alternatives. Use before implementing anything non-trivial, or when asked to design, architect, or choose an approach.

romerma/mstack

Skill Claude CodeCodex

Implement one work item with the tests that prove it, keeping durable state current and recording the requirement-to-test map, then hand it to a different pass to judge. Use when starting to write code for an item, or when asked to implement, build, or fix something under mstack.

romerma/mstack

Skill Claude CodeCodex

Run a program of work across many changes, tracks and sessions, with isolated worktrees, briefs a stranger could execute, and continuous landing. Use only for multi-session programs; single-session work should use the feature route instead.

romerma/mstack

Skill Claude CodeCodex

Review a finished session for what should change in the workflow itself, deciding for each lesson which document or check should absorb it. Use after closing an item, after something went wrong, or when asked to run a retro or improve the process.

romerma/mstack

Skill Claude CodeCodex

Judge work that already exists against its requirements, its tests and the real diff, using reviewers that did not write the code. Use to review a branch, a PR, or a diff, or when asked whether a change is ready.

romerma/mstack

Skill Claude CodeCodex

Start a task under the mstack workflow. Matches the request to a playbook, copies its steps into the todo list, and routes through understand, design, spec, implement, verify, review and ship. Use for /mstack, or when the user asks to work rigorously, to verify something properly, or to run a task end to end.

romerma/mstack

Skill Claude CodeCodex

Initialize mstack in a repository, creating the durable state directory and seeding the work queue from what the repo already tells you. Use once per repository, when mstack reports no .mstack directory, or when asked to set up or install mstack here.

romerma/mstack

Skill Claude CodeCodex

Take a verified change through review threads, CI and the merge gate to a merged state. Use to open or land a PR, to get a change merged, or when asked to ship or babysit something to green.

romerma/mstack

Skill Claude CodeCodex

Write and adversarially review a specification before any code is written, with stable requirement ids, EARS statements and a task list that maps back to them. Use on the opt-in spec path, when an item is marked sdd, when a change crosses several subsystems, or when asked to write a spec or requirements.

romerma/mstack

Skill Claude CodeCodex

Build a traced mental model of a subsystem before changing it, covering both how it works now and why it ended up this way. Use before designing or fixing anything in unfamiliar code, or when asked how something works, why a decision was made, or to explain a part of the codebase.