Assess Impact
Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?".
Install
npx skills add danielvm-git/bigpowers --skill assess-impactgit clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p ~/.claude/skills
cp -r /tmp/bigpowers/.cline/skills/assess-impact ~/.claude/skills/assess-impactPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Assess Impact > **HARD GATE** — Run this skill before `plan-work` whenever a change touches an existing module, symbol, or file used by more than one caller. Skip only for net-new code with no existing dependents. Find the blast radius of the proposed change before a single line is written. ## Modes - Default: full impact analysis (dependents + affected stories + test coverage mapping) - --lightweight: Fast fan-in/fan-out only (<10s). Maps callers and imports without test coverage mapping. Used by build-epic step 2 as a pre-plan gate. Risk score > 7 triggers a mandatory grill-me session before proceeding. ## Process ### 1. Identify the target Name the symbol, module, or file being changed. If the user hasn't specified, ask one question: "What exactly are you changing?" ### 2. Find dependents ``` grep -rn "[symbol-name]" . --include="*.ts" | grep -v node_modules git log --oneline -10 -- [file-path] ``` → verify: `test -f specs/IMPACT_LATEST.md || test -d specs/bugs` ### 3. Map to release plan stories Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change. → verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml` ### 4. List test coverage Find tests that exercise the target: ``` grep -rn "[symbol-name]" . --include="*.test.*" --include="*.spec.*" ```
Details
- Skill name
assess-impact- Repository
- danielvm-git/bigpowers
- Path
.cline/skills/assess-impact/SKILL.md- License
- MIT
- Repo updated
- 9 November 2026
FAQ
What does the Assess Impact skill do?
Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?".
How do I install the Assess Impact skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add danielvm-git/bigpowers --skill assess-impact. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Assess Impact popular?
It lives in danielvm-git/bigpowers, which has 292 GitHub stars and 23 forks.
Related skills
Align Grid
292danielvm-git/bigpowers
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay that lives in the SAME content box as the content, subgrid "bands" so every element snaps to a column line, an 8px baseline lock, and runtime OPTICAL ALIGNMENT that puts display type's i
Audit Code
292danielvm-git/bigpowers
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.
Audit Plan
292danielvm-git/bigpowers
Evaluate an incoming project plan against bigpowers principles and conventions, surface gaps, and produce a READY/NOT READY verdict before engagement begins. Use when a new project arrives, when adapting a foreign plan, or before running seed-conventions on an unfamiliar codebase.
Comparative Evaluation
207Owl-Listener/ai-design-skills
A/B testing, side-by-side comparison, and preference ranking for AI outputs.
Dspy Custom Module Design
125OmidZamani/dspy-skills
Use for creating custom DSPy modules, extending dspy.Module, reusable components, stateful modules, serialization, and module testing.
Enforce First
292danielvm-git/bigpowers
Apply the F.I.R.S.T test quality rubric (per CONVENTIONS.md §Tests) to a test suite or individual tests. Use when develop-tdd is writing tests, when test quality needs to be checked, or when user mentions F.I.R.S.T or "test quality".
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.