audit-plan-remediation

Convert validated audit findings into prioritized remediation plans with owners, dependencies, and rollback guidance.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill audit-plan-remediation-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-plan-remediation
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/audit-plan-remediation
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill audit-plan-remediation-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a reviewed list of audit findings into an executable, prioritized remediation plan is slow and error-prone: dependencies get missed, severity ordering is inconsistent, and rollback or approval requirements are forgotten. This Skill converts validated audit findings into a structured remediation plan with owners, complexity estimates, verification steps, rollout, and rollback guidance. ## Core Features & Use Cases - Dependency-aware prioritization: Builds a directed dependency graph from finding prerequisites, shared root causes, and release constraints, rejecting cycles and ordering containment and critical security findings first. - Complexity estimation and phasing: Estimates each item as low, medium, high, or very-high complexity with recorded rationale, and groups work into stable milestone phase IDs that downstream execution skills can consume. - Schema-validated outputs: Emits reports/audit-remediation-plan.json (schema version 2.1.0, bound to the source review's auditRunId and SHA-256 digest) plus a Markdown version preserving ordering and traceability. - Use Case: After audit-review-findings confirms a set of security findings, invoke this Skill to produce a phased remediation plan where each item has an owner role, acceptance criteria, tests, approvals, and rollback steps, ready for audit-remediation to execute. ## Quick Start Use the audit-plan-remediation skill to turn the reviewed findings in reports/code-audit-review.json into a prioritized remediation plan with phases, owners, and rollback steps.

Frequently Asked Questions about audit-plan-remediation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn audit findings into a remediation plan?

Run this Skill after findings have been reviewed and confirmed. It validates the reviewed findings report, builds a dependency graph, prioritizes containment and critical security items, and emits a JSON and Markdown remediation plan with owners, acceptance criteria, rollout, and rollback steps.

What input does the remediation planning skill require?

It requires a reviewed findings report such as reports/code-audit-review.json or reports/azure-audit-review.json produced by audit-review-findings, validated against the audit-findings-review schema. Raw or unreviewed findings are rejected.

Does this skill execute the remediation work itself?

No. It only plans the work. Execution is exclusively owned by the separate audit-remediation skill, which consumes the plan's stable milestone phase IDs to run items in dependency order.

How are remediation items prioritized and estimated?

Mandatory containment and critical or high security findings come first, then ordering by dependency criticality, severity, exploitability, user impact, confidence, complexity, and cost. Each item is estimated as low, medium, high, or very-high complexity with recorded rationale.

What happens when findings are disputed or need more evidence?

Findings marked needs-more-evidence, disputed, or false-positive are explicitly dispositioned in the plan rather than silently dropped. No unsupported repairs are scheduled, and accepted risk requires explicit approval.

Why does plan generation fail on cyclic dependencies?

The Skill builds a directed dependency graph and rejects cycles until they are resolved or explicitly broken into phases. This fail-closed behavior prevents execution orders that would violate prerequisites.