ワンクリックで
scope-control
Use when any task is received — silently enforces smallest viable change set and proposes decomposition for large tasks
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when any task is received — silently enforces smallest viable change set and proposes decomposition for large tasks
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | scope-control |
| description | Use when any task is received — silently enforces smallest viable change set and proposes decomposition for large tasks |
| tags | ["gate","scope","discipline"] |
| triggers | ["always"] |
| chains_to | ["ralph-loop","writing-plans"] |
| priority | gate |
| gate | true |
Three rules. No essays. Applied silently.
Use when a structured PRD document is needed for the ralph loop — generates prd.json and progress.txt
Use when task scope exceeds one context window and decomposes into independent pass/fail stories with clean iteration boundaries
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — merge, PR, or cleanup
Use when starting feature work that needs isolation from the current workspace or before executing plans that could leave the branch in a broken state
Use when a hard problem was just solved and the solution should be captured as a learning for future reference
Use when 3+ distinct occurrences suggest a skill should be updated with a new trigger, anti-pattern, or verification step