Repository intake
Map structure, risks, and owner context before edits begin.
Commands
Give Claude Code a controlled command bench.
ccprompts packages 70 slash commands, 10 specialist agents, and validation workflows into one installable operating surface for real engineering decisions.
Installation guides
01 / governed execution
Set the authority before the agent acts.
A command library is only useful when the boundaries are visible. Adjust the run scope and the ledger updates with the checks that should happen before a change leaves the machine.
Run scope
Controls how much automation a command may perform before human review.
3/5
inspectmodifyrelease
execution ledgerreview required
02 / command catalog
Find the next engineering move.
Search the real catalog, filter by lifecycle phase, then copy a command into Claude Code. The interface is built for recall and attribution, not browsing theater.
esc clears
0 commands shownenter copies selected command
03 / playbooks
Reusable workflows, not vague use cases.
Each playbook maps to an operational pattern: scan, change, verify, and hand off with evidence attached.
/analyze-project
Security review
Run secrets, dependency, and surface-area checks with clear findings.
Release handoff
Prepare changelog, version notes, checks, and rollback language.
Team onboarding
Turn a repository into a guided brief for the next contributor.
04 / lifecycle map
A command for every handoff.
Click a phase to filter the catalog. Counts and phase numbers stay visible so the system remains auditable.
05 / quickstart
Install it where the work happens.
Add the marketplace, install the plugin, restart Claude Code, and the catalog appears under /help. Teams can pin the same setup in repo settings.
claude code
Start with the command bench.
Install the plugin, run the first scan, and make Claude Code operate from visible controls instead of loose prompts.
/
plugin install ccprompts@ursisterbtw