danielvm-git/bigpowers
44+ agent skills for high-integrity, spec-driven, test-first software engineering. A prescriptive methodology for orches
Actual rules from this repo
Path in source repo: .cursor/rules/assess-impact.mdc · format: mdc
---
description: "Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?"."
alwaysApply: false
---
# 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.
## 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: `grep -rn "[target]" . | wc -l`
### 3. Map to release plan stories
Read `specs/RELEASE-PLAN.md` (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: `grep -c "Story" specs/RELEASE-PLAN.md 2>/dev/null || echo "no release plan"`
### 4. List test coverage
Find tests that exercise the target:
```
grep -rn "[symbol-name]" . --include="*.test.*" --include="*.spec.*"
```
→ verify: `grep -rn "[target]" . --include="*.test.*" | wc -l`
### 5. Classify risk
| Level | Condition |
|-------|-----------|
| Low | ≤ 2 callers, all covered by tests |
| Medium | 3–10 callers, partial test coverage |
| High | > 10 callers, or shared API/interface, or no tests |
### 6. Write specs/IMPACT.md
```
## Target
[symbol or file being changed]
## Dependents ([count])
- [file]: [caller or usage]
## Affected Stories
- Story [X.Y]: [title]
## Test Coverage
- [test file]: covers [scenario]
- Gap: [untested behavior]
## Risk: Low / Medium / High
[One-sentence rationale]
## Recommended action
[Proceed / Add tests first / Discuss design]
```
→ verify: `grep "Risk:" specs/IMPACT.md`
Suggest `plan-work` once risk is understood and any test gaps are noted.
Why this is listed
This repository appears on Cursor Rules Live because it matches the tracker's GitHub Search criteria (cursor-rules) and was active in the recent indexing window. The tracker refreshes every 15 minutes, so the metadata above reflects the state at the most recent index pass. If the data here looks stale, the source repository may have been archived or moved out of the tracked topic; the next cron tick will reconcile.