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
- Define in-scope work.
- Define out-of-scope work.
- List blockers and their impact.
- 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