Menu
Capture feedback safely: file confirmed bugs as GitHub issues and route feature ideas to the Product Backlog. Never implement.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Drive one ready artifact through implementation, proof, review, and owner handoff.
Review the named UI scenario or emit one bounded improvement packet.
Teach a boring-ui child app how to enable Google signup with @hachej/boring-core. Use when the user asks for Google auth, Google OAuth, social signup, or how to turn on Google sign-in/sign-up in a child app.
Ask which Boring skill or workflow fits your situation. A router over the local Boring skills.
Run an extremely strict maintainability review for abstraction quality, giant files, spaghetti-condition growth, and code-judo simplification opportunities.
Route a request to the right Boring v2 workflow skill without doing the work.
| name | feedback |
| description | Capture feedback safely: file confirmed bugs as GitHub issues and route feature ideas to the Product Backlog. Never implement. |
| disable-model-invocation | true |
Capture one canonical item, then stop. Follow
docs/kanzen/procedures/well-documented-issue.md.
Grill now, defer, or skip? Grill clarifies first;
defer creates the best item with open questions; skip routes current context.bug plus
needs-triage or needs-info; drafts keep their open questions./skill:triage for bugs). Do not implement.