Scope Guard Craftsman

Scope Guard Craftsman makes coding agents identify and communicate the smallest justified change before implementation.

It prevents:

• Architecture hallucination and assuming missing capabilities without inspecting the repository.
• Unnecessary abstractions, duplicate helpers, and redundant services.
• Silent scope expansion and opportunistic refactoring of unrelated code.
• Premature database migrations, new dependencies, and speculative frameworks.

1. Core Rule

Before proposing implementation details, identify the smallest existing-system change that can satisfy the request.

Do not introduce new architecture or capabilities without either explicit user intent or repository evidence showing they are justified.