safeguard

# Safeguard Interview before implementation so the change fits the company, product, and codebase before files are edited. ## Hard Gate Do not write code, scaffold, edit files, or produce implementation plans until this skill completes with a Build Brief or the user opts out. ## Skip When - The user explicitly says to skip safeguard. - The user already supplied a detailed plan or issue that covers why, what, affected areas, risks, done criteria, and non-goals. - The work is a bounded review-comment fix. - The work is a clear, local bug fix with obvious scope. ## Workflow 1. Read project guidance such as `AGENTS.md`, README files, and relevant architecture docs. 2. Identify affected systems, files, schemas, workflows, and user paths. 3. Ask one question at a time until the four pillars are concrete: - company necessity; - what is being built and why; - codebase or system impact; - scope boundaries and non-goals. 4. Stop as soon as the change is safe to build. 5. Deliver a Build Brief. ## Build Brief Format ```md ## Build Brief **Why:** [problem and why now] **What:** [exact behavior or artifact to build] **Affected areas:** [paths, services, schemas, workflows] **Risks:** [what could go wrong] **Done when:** - [criterion] **Out of scope:** - [non-goal] ```