Scope Guard FAQs

Question 1

How does Scope Guard calculate feature worthiness?

Accepted Answer

It uses a scoring formula that balances Value Factors (Business Value, Time Criticality, Risk Reduction) against Cost Factors (Complexity, Token Cost, Scope Drift) to produce a numerical priority score.

Question 2

How does it handle deferred features?

Accepted Answer

Features that score low or exceed the branch budget are moved to a structured backlog directory (docs/backlog/) with their scores and context preserved for monthly re-evaluation.

Question 3

Can it be used during AI-driven brainstorming?

Accepted Answer

Yes, it specifically integrates with brainstorming workflows to force an explicit evaluation of every proposed component before design documentation begins.

Question 4

When should I avoid using Scope Guard?

Accepted Answer

It is not intended for bounded bug fixes, documentation-only changes, or trivial single-file edits under 50 lines where the overhead of evaluation exceeds the implementation effort.

Question 5

What are the default branch monitoring thresholds?

Accepted Answer

Scope Guard monitors for 'Yellow' and 'Red' zones at 1000/2000 lines, 15/30 commits, and 3/7 days respectively to prevent branches from becoming unmanageable.

Scope Guard

Key Features

Use Cases

Scope Guard

Key Features

Use Cases