splock

A governed plan → implement → verify lifecycle for Claude Code, with a deterministic enforcement spine.

splock is an Anthropic Claude Code plugin. It turns ad-hoc agent work into a structured, reviewable lifecycle: you plan an initiative into an explicit specification, implement it task by task, and verify each task against a completion gate that an executing agent cannot talk its way past. The parts of the system that matter for correctness and safety live in deterministic code — shell hooks and CLI exit codes — not in prose an agent could ignore or a hostile input could overwrite.

Why splock exists

A capable coding agent left to free-form on a real codebase tends to: skip the plan, drift from scope, edit files outside its lane, declare success without running tests, and quietly weaken the very guardrails meant to stop it. Prompts that say "please run the tests" or "do not touch sealed files" are advisory — an agent can rationalize past them, and adversarial content the agent merely reads can instruct it to.

splock's answer is to move every load-bearing decision out of the model:

A written plan precedes code. The planner emits a schema-valid plan substrate and a rendered Markdown twin. The substrate is sealed — surgical changes go through a dedicated amend path, never a raw edit.
Work is gated, not trusted. Each task carries explicit success criteria and an enabled test set. A separately-pinned verifier decides readiness; the coder cannot self-certify.
Boundaries are enforced in hooks. Sealed paths, suppression patterns, unsafe package installs, and raw DDL are blocked by PreToolUse hooks that return a non-zero exit code. Enforcement never depends on agent prose.
State is the source of truth. Orchestrator and plan state are JSON files mutated only through a CLI, validated against JSON Schema, and append-only where it matters.

The result is a workflow you can hand to an autonomous or semi-autonomous agent and still reason about what it is structurally prevented from doing.

The lifecycle

splock ships a set of slash commands and the subagents and skills behind them:

Stage	Command	What it does
Reconnaissance	`/recon`	Survey the codebase / problem space before committing to a plan.
Research	`/research`	Deeper external/internal investigation feeding a plan.
Q&A	`/qna`	Capture an interactive Q&A log that a plan can ingest.
Plan	`/plan`	Two-call planner → schema-valid plan substrate + Markdown twin.
Implementation plan	`/implplan`	Expand a plan into an orchestrator DAG of tasks with dependencies.
Code	`/code`	Execute a task under the completion gate (write code, run tests, iterate).
Test	`/test`	Run the enabled test set across the plan / at a phase gate.
Review	`/review`	Sonnet-class review at phase boundaries.
QA	`/qa`	Adversarial review of a plan or an implementation.
Wrap	`/wrap`	Fold an exploratory artifact into the plan record.

The two-call planner separates free-form reasoning (call 1) from constrained, schema-valid JSON emission (call 2). The completion gate ("Ralph gate") runs the coder in a retry loop and refuses to declare a task done until an independent verifier confirms a green test run.

The fleet status hub (opt-in)

Projects running many slugs at once can opt into fleet — a concurrency-safe lifecycle tracker with a generated status hub. State lives in per-slug files (docs/plans/<slug>/_fleet.json + an append-only event log), so any number of agents update concurrently with zero write contention; the hub .md's FLEET:* zones are a derived view regenerated by bin/fleet render --write. Stage commands and engines record wip on start and ready --next <next stage> (or done / blocked / closed) on completion automatically — agents never hand-edit the hub, and the per-slug state files are sealed so they can't. Opt in with bin/fleet init; convert an existing hand-edited launcher with bin/fleet init --hub + migrate + seed.

splock

A governed plan → implement → verify lifecycle for Claude Code, with a deterministic enforcement spine.

Why splock exists

splock's answer is to move every load-bearing decision out of the model:

A written plan precedes code. The planner emits a schema-valid plan substrate and a rendered Markdown twin. The substrate is sealed — surgical changes go through a dedicated amend path, never a raw edit.
Work is gated, not trusted. Each task carries explicit success criteria and an enabled test set. A separately-pinned verifier decides readiness; the coder cannot self-certify.
Boundaries are enforced in hooks. Sealed paths, suppression patterns, unsafe package installs, and raw DDL are blocked by PreToolUse hooks that return a non-zero exit code. Enforcement never depends on agent prose.
State is the source of truth. Orchestrator and plan state are JSON files mutated only through a CLI, validated against JSON Schema, and append-only where it matters.

The result is a workflow you can hand to an autonomous or semi-autonomous agent and still reason about what it is structurally prevented from doing.

The lifecycle

splock ships a set of slash commands and the subagents and skills behind them:

Stage	Command	What it does
Reconnaissance	`/recon`	Survey the codebase / problem space before committing to a plan.
Research	`/research`	Deeper external/internal investigation feeding a plan.
Q&A	`/qna`	Capture an interactive Q&A log that a plan can ingest.
Plan	`/plan`	Two-call planner → schema-valid plan substrate + Markdown twin.
Implementation plan	`/implplan`	Expand a plan into an orchestrator DAG of tasks with dependencies.
Code	`/code`	Execute a task under the completion gate (write code, run tests, iterate).
Test	`/test`	Run the enabled test set across the plan / at a phase gate.
Review	`/review`	Sonnet-class review at phase boundaries.
QA	`/qa`	Adversarial review of a plan or an implementation.
Wrap	`/wrap`	Fold an exploratory artifact into the plan record.

splock

Popularity

What's Inside

Confidence

README

splock

Why splock exists

The lifecycle

The fleet status hub (opt-in)

Similar Plugins

ecc

octo

claude-code-harness

supergraph

splock

Why splock exists

The lifecycle

The fleet status hub (opt-in)

Popularity

Health & Quality

Similar Plugins

ecc

octo

claude-code-harness

supergraph

planning-with-files

superpowers