fix-plan-blast-radius
Plan the smallest correct fix at the right trust boundary, listing siblings, callers, adjacent journeys, contract changes, data impact, rollback, and approvals before writing code. Use for every non-trivial fix and always for security, payment, auth, or data bugs.
71
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix Plan and Blast Radius
Fill templates/fix-plan.md:
- Fix location: the layer that owns the rule (server for access, payments, and validation; template for rendering; job for async).
- Smallest change; a shared helper when the class appears more than once (
requireOwner,safePath,parsePublicUrl,toPublic, an idempotency store). - Siblings: search patterns and hits (see
fix-class-sweep). - Callers and adjacent journeys at risk, mapped to the tester's guard tests.
- Contract change? List every field, status code, or shape that changes. In our lab an allow-list serializer silently dropped
ownerand broke a journey. - Customer-visible or policy change? Then NEEDS-PRODUCT-DECISION.
- Data impact and repair plan.
- Rollback: revert, flag, or config switch.
- Approvals: deploys, data repair, and policy only.
Exit criteria
The plan is complete, and approvals are requested in one batch if needed.
Counterpart of tester skill: qa-recon-risk-map.
- Repository
itsablabla/qa-bug-agent-skills
- Revision
9a6f628
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.