Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From splock
Run a phase-boundary review gate (plan_to_implplan or implplan_to_code) via bin/verify. Use when the user says "review the phase boundary", "run the review gate for X", or when an orchestrator junction of kind review_gate must be cleared before the DAG advances to the next phase.
How this skill is triggered — by the user, by Claude, or both
Slash command
/splock:reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Phase-boundary review gate. Runs `bin/verify` for a named junction.
Phase-boundary review gate. Runs bin/verify for a named junction.
Operator entry: /review <slug> <junction>, where <junction> is a
phase-boundary id (e.g. plan_to_implplan, implplan_to_code).
Spawns the reviewer subagent (agents/reviewer.md) — the evaluator-optimizer
junction reviewer that decides whether the boundary is cleared.
npx claudepluginhub splockorg/splock --plugin splockCreates, edits, and verifies skills using a test-driven development approach with pressure scenarios and subagents.