From loop-engineering
Check token budget and run-log spend before and after a loop run. Enforces early exit when over budget or when there is no actionable work.
How this skill is triggered — by the user, by Claude, or both
Slash command
/loop-engineering:loop-budgetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run at the **start** and **end** of every loop iteration.
Run at the start and end of every loop iteration.
loop-budget.md for daily caps and kill-switch flags.loop-run-log.md (last 24h).tokens_estimate for the active pattern today.loop-pause-all is set → exit immediately with a one-line note in STATE.md.Append one JSON object to loop-run-log.md:
{
"run_id": "<ISO8601>",
"pattern": "<pattern-id>",
"duration_s": <number>,
"items_found": <number>,
"actions_taken": <number>,
"escalations": <number>,
"tokens_estimate": <number>,
"outcome": "no-op | report-only | fix-proposed | escalated"
}
max sub-agent spawns/run from loop-budget.md.loop-budget.md under Alerts This Period.npx claudepluginhub sergevatel/loop-engineeringGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.