scope-guard

Scope creep prevention starts with worthiness scoring that weighs business value, time criticality, and risk reduction against complexity, token cost, and scope drift. Document decisions with backlog and branch-budget implications before starting work to enforce discipline and justify trade-offs.

Evaluate feature worthiness by scoring business value, time criticality, and risk reduction divided by complexity, token cost, and scope drift. This framework surfaces overengineered proposals and ensures only justified work enters the backlog.

Branch-budget monitoring applies threshold constraints to track scope drift as work progresses. Record decision documentation and budget implications at brainstorming and planning stages so branches stay within acceptable size and complexity bounds.

Backlog comparison surfaces duplicate or lower-priority work before it consumes resources. This comparison step prevents committing to features that conflict with existing priorities or repeat work already planned.

Yes. Scope-guard applies across brainstorming, planning, and branch-threshold monitoring phases. It's designed to catch overengineering decisions early when course correction is lowest-cost, before implementation begins.

Features failing worthiness scoring are flagged as low-value or overengineered and documented with decision rationale. This prevents them from entering the backlog or branch work without explicit stakeholder override and clear risk acknowledgment.