Boring Loop Grill
SkillDev toolsUse for /loop-grill: clarify one Kanzen issue with grill-me and ask-user, then return it to triage or keep it blocked.
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 Grill 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-grill/SKILL.md and read by ahel’s review.
Make an unclear issue clear enough to route. Do not plan deeply. Do not implement.
Steps
- Read the issue, comments, captured context, screenshots, and nearest code/docs.
- Self-answer anything the repo can answer quickly.
- Ask only questions that change routing, acceptance, proof, or risk.
- Use grill-me style questions; use ask-user for async owner input.
- Write the clarified summary, acceptance, proof path, and open risks back to the issue.
Exit
- Still unclear:
state:blocked phase:grill track:owner, gateclarity. - Clear enough:
state:queued phase:triage track:owner, gatetriage. - Not worth doing:
state:done, with a short reason.
For async grill, leave one pending ask-user session with issue URL/title, why it
is blocked, the questions, answer format, and resume command
/loop-grill <issue>.
Signals
- GitHub stars
- 46
- Forks
- 2
- Last commit
- Sep 2026
Others that do the same job
Advanced
- Catalog kind
- skill
- Gateway key
boring-loop-grill- Source
- github.com/hachej/boring-ui