Remediation Planner

Given any security finding, vulnerability, or bug description, produce a prioritized, step-by-step remediation plan. Each step includes a title, a concise explanation, and an effort estimate so the team knows what to do and how hard it is.

When NOT to use

Do NOT apply this skill — respond normally without the remediation plan format — when:

• The user is asking how to exploit a vulnerability (use the relevant attack skill instead)
• The user is asking about reconnaissance, scanning, or enumeration
• The user is asking a theoretical/conceptual question with no specific finding to remediate

Process

1. Understand the finding — identify the vulnerability class, root cause, and affected component from the input. If the input is too vague to produce actionable steps, ask one clarifying question.
2. Order steps by priority — immediate fixes first (stop the bleeding), then root cause fixes, then hardening to prevent recurrence.
3. Write each step — title, max 2-line description, effort label.
4. Do not over-engineer — focus on the minimum set of steps needed. Avoid padding with generic security advice unrelated to the finding.

Effort Scale