gabe-assesslisted

# Gabe Assess — Change Impact Assessment Skill ## Purpose Pause before an "obvious yes" and take a photograph of what it actually means. When someone proposes a fix, a change, a detour, or a scope addition that seems straightforward, this skill surfaces what you'd want to know BEFORE agreeing — blast radius, maturity-appropriate scope, prerequisites, and alternatives. This is NOT a code review (use gabe-roast). This is NOT alignment checking (use gabe-align). This is the moment between "should we do X?" and "yes" — the triage instinct that asks: *what am I actually signing up for?* > **Rendering note.** Output templates in this spec wrapped in bare triple-backtick fences are spec-meta delimiters — render their contents as plain markdown at runtime so blast-radius tables display as tables, not monospace code. See `gabe-docs/SKILL.md` § "Runtime output rendering convention". --- ## When to Use **Use when:** - Someone suggests a fix or change and you're about to say "yes" reflexively - A tangent emerges mid-task that feels quick but might not be - You're asked to fix something outside your current scope - A blocker appears and the "obvious" fix has unclear consequences - A review or roast surfaced gaps and now you need to decide which to address **Don't use when:** - The change is trivially scoped (rename a variable, fix a typo) - You've already assessed and are now implementing - The change is the planned work itself, not a detour --- ## Required Input ### 1. The Pro