메뉴
Use 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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
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.
SOC 직업 분류 기준
| name | boring-loop-plan |
| description | Use 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. |
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.
docs/issues/<issue-number>/plan.md or plan-<slice>.md.state:active phase:implement track:owner.state:blocked phase:grill track: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.