Boring Loop Plan
SkillDev toolsUse for /loop-plan: turn a Kanzen issue or PR that is too risky, unclear, large, or multi-slice for direct implementation into an issue-linked plan with acceptance, flag path, proof, review budget, and next slice.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Boring Loop Plan skill
What this skill tells your AI
The instructions your AI receives, as published by hachej/boring-ui in .agents/skill-library/kanzen/v1/boring-loop-plan/SKILL.md and read by ahel’s review.
Create the smallest useful plan for one GitHub issue.
Canonical model: ../../../../../docs/kanzen/boring-loop.md.
Plan file rules: ../../../../../docs/kanzen/procedures/issue-plans.md.
Trunk/flag/review budget: ../../../../../docs/kanzen/procedures/trunk-flags-review-budget.md.
Steps
- Read the issue, related PRs, newest owner comments, existing plan files, and relevant code/docs.
- Decide whether inline issue planning is enough or a plan file is required.
- If a plan file is required, create or update
docs/issues/<issue-number>/plan.mdorplan-<slice>.md. - Include: decision, flag/abstraction path, acceptance, slices, proof, open blockers.
- Keep slices near the review budget; propose stacked PRs only when needed.
- Run thermo review on risky, broad, or multi-PR plans.
- Comment the next action and session id on GitHub.
- Update labels to the first unmet next gate.
Exit
- Clear enough for code:
state:active phase:implement track:owner. - Still blocked:
state:blocked phase:grill track:owner. - Plan-only done and waiting for owner:
state:ready phase:merge track:owner.
Return a short card with URL, primary issue, plan file, flag, proof path, review budget, blockers, and exact next action.
Signals
- GitHub stars
- 46
- Forks
- 2
- Last commit
- Sep 2026
Others that do the same job
Advanced
- Catalog kind
- skill
- Gateway key
boring-loop-plan- Source
- github.com/hachej/boring-ui