Menu
Use for scheduled /triage: refresh GitHub, run the first unmet gate, collect proof, and merge only fast-track-safe PRs.
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.
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.
Based on SOC occupation classification
| name | boring-orchestration |
| description | Use for scheduled /triage: refresh GitHub, run the first unmet gate, collect proof, and merge only fast-track-safe PRs. |
Run scheduled /triage.
Canonical model: ../../../../../docs/kanzen/boring-loop.md.
How-to details: ../../../../../docs/kanzen/procedures/.
boring-triage.| Gate | Action |
|---|---|
intake | repair issue body: context, redaction note, first plan |
triage | run boring-triage; classify first real gate |
clarity | use boring-loop-grill; grill-me plus ask-user when async |
risk | keep track:owner; upgrade only when fast-track rules pass |
flag | require not-needed, safe feature flag, or abstraction path |
plan | use boring-loop-plan; issue-linked plan for risky or multi-PR work |
implementation | use boring-loop-implement; one parent lane owns one issue/PR |
proof | tests, CI, proof-of-work comment, screenshots, and demo proof when useful |
merge | fast-track merge if all gates pass, otherwise owner review |
state:*, phase:*, track:*, optional source:feedback.../../../../../docs/kanzen/procedures/trunk-flags-review-budget.md.../../../../../docs/kanzen/procedures/issue-plans.md.../../../../../docs/kanzen/procedures/proof-of-work.md.../../../../../docs/kanzen/procedures/coding-rules.md.../../../../../docs/kanzen/procedures/visual-review.md.../../../../../docs/kanzen/boring-loop.md.track:owner.