Scope Check

• Appear in the roadmap or task list? → Proceed, no gate needed.
• Extend an existing planned feature? → Proceed, note the extension.
• Introduce something entirely new? → Flag it.

Rules

• Never block enthusiastically requested work. If the user is excited about a feature, the scope check is informational, not a gate. Build it.
• Never say "this is out of scope" as a refusal. You're flagging, not refusing. The user always decides.
• Keep it invisible when things match. If the feature is in the plan, don't announce "scope check passed." Just build.
• One sentence max for the flag. Don't explain why scope matters or what the roadmap says. The user wrote the roadmap — they know.

Chain Hints

After scope-check passes, the normal flow continues:

• plan-first — if the task is complex enough to need a plan
• scope-guard — during implementation, to prevent over-delivery