Menú
Drive one ready artifact through implementation, proof, review, and owner handoff.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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.
Create a GitHub issue from user feedback with safe context and simple labels. Never implement.
| name | exec |
| description | Drive one ready artifact through implementation, proof, review, and owner handoff. |
| disable-model-invocation | true |
Drive one executable TODO, plan, Beads epic, or validated UI packet to
ready-for-human; never merge.
Read the artifact, docs/kanzen/boring-loop.md, and
docs/kanzen/MODEL-CARD.md. Load only the needed procedure:
docs/kanzen/procedures/worktree-agent.mddocs/kanzen/procedures/proof-of-work.mddocs/kanzen/procedures/visual-review.mddocs/kanzen/procedures/owner-review-card.md../../skill-references/exec/index.mdRequire clear scope, acceptance, proof, dependencies, and risk; repair planning
gaps through /skill:plan and stop on unresolved human intent.
Implement the smallest bounded slice with behavior tests, record current proof,
apply the Model Card review ladder and mandatory code-thermo gate, and integrate
or disposition every material finding. Re-prove and re-review non-trivial fixes.
Then open/update the PR and send the owner card through ask_user (PR comment
fallback), attaching the best runnable UI or file/proof artifact.
For a UI packet, validate it first and follow the complete round, stop, baseline,
and Inbox rules in visual-review.md; the packet grants no edit or merge
authority.
Exit only with green proof or an explicit waiver/residual risk, current required reviews, a human-runnable validation path, and a clear next action.