Turboshovel
Persistent Workflows for Claude Code
Enforce process. Track progress. Resume anytime.
Powered by Rundown runbooks.
Features
Persistent State
Workflow progress survives context clears. Resume interrupted tasks instantly. Never lose track of where you are.
Process Enforcement
Enforce multi-step workflows with Rundown runbooks. Prevent agents from skipping steps or jumping around.
Quality Gates
Run lint, test, build at workflow boundaries. Block agents when checks fail. Chain gates for complex pipelines.
Context Injection
Auto-inject context at runbook steps. Agents get focused, step-specific instructions exactly when needed.
Quick Start
1. Install the plugin:
claude plugin add tobyhede/turboshovel
2. Create a runbook .claude/rundown/runbooks/feature.runbook.md:
## 1. Create Plan Design the implementation approach. - PASS: CONTINUE - FAIL: STOP ## 2. Implement Feature Write the code following the plan. - PASS: CONTINUE - FAIL: RETRY 2 ## 3. Run Tests Verify everything works. - PASS: COMPLETE - FAIL: GOTO 2
3. Add quality gates in .claude/turboshovel.json:
{
"gates": {
"test": {
"command": "npm test",
"on_fail": "BLOCK"
}
}
} How it works:
- → Runbook defines the workflow steps and transitions
- → State persists in
.claude/rundown/session.json - → Context clears?
rundown statusshows where you are - → Gates enforce quality at each step boundary
Context Conventions
Files in .claude/context/ are automatically injected based on naming patterns
| Pattern | When Injected |
|---|---|
| session-start.md | Session start |
| {name}-start.md | Command or skill start |
| {name}-stop.md | Agent or skill completion |
| PostToolUse.md | After any tool use |
| UserPromptSubmit.md | Before prompt submission |
Example: code-review-start.md is injected when /code-review skill starts