scope-rescue

name	scope-rescue
description	Reduce an overgrown milestone into a realistic vertical slice with explicit cuts, preserves, and risks. Use when the plan is too broad, behind schedule, or internally inconsistent.

Scope Rescue

When to use

Reduce an overgrown milestone into a realistic vertical slice with explicit cuts, preserves, and risks. Use when the plan is too broad, behind schedule, or internally inconsistent.

Inputs to gather

• current scope
• deadline/team limits
• must-keep fantasy
• quality bar

Recommended roles

• executive_producer
• creative_director
• technical_director

Primary docs / outputs

• studio/docs/active/milestones.md
• studio/docs/active/current-sprint.md
• studio/docs/active/risk-register.md

Workflow

1. Inspect the current repo/docs state first and cite concrete evidence.
2. Choose the smallest useful output that moves the project forward.
3. Update or create durable docs when the result should persist.
4. Recommend the next best role or skill if more work remains.

Category rules

• Inspect the repo, existing docs, and engine clues before asking for more information.
• Use minimal clarifying questions only when a missing fact blocks a good recommendation.
• Write or update durable docs when the output should survive chat history.

Deliverables

• cut list
• reframed slice
• dependency changes
• risk-aware next milestone

Validation bar

• updated active docs
• recommended next skill
• critical unknowns listed