scope-and-blockerslisted

# Scope And Blockers ## Purpose Keep scope and blockers explicit. ## When to Use Use when requirements are broad, ambiguous, or blocked by missing information. ## Inputs User request, plan, constraints, assumptions, dependencies. ## Steps 1. Define in-scope work. 2. Define out-of-scope work. 3. List blockers and their impact. 4. Continue with safe assumptions when possible. ## Gates No hidden expansion of scope; blockers are visible. ## Evidence Plan, issue list, or final response names skipped and blocked items. ## Anti-Patterns Silently changing the goal; stopping early without naming the blocker. ## Related `assumption-registry`, `goal-delivery-completeness`