Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    action plan

    1

    Convert design reviews and audits into sequenced remediation roadmaps with risk scores and rollback plans.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    action plan

    action plan

    Example session with this skill installed

    Read the design-review.md in docs/remediation and create an action plan. We have a release freeze in two weeks and low capacity for the backend team.

    • Read your context and instructions
    • Compiled the action plan

    I have processed the findings from docs/remediation/design-review.md. I applied your constraints regarding the two-week release freeze and limited backend capacity. High-priority containment for the security findings is scheduled for this week, while backend structural changes are deferred to the hardening phase.

    Remediation Action Plan Summary

    IDFindingPhasePriorityEffortOwner
    A-001F-SEC-001: SQL Injection risk in authContainmentCriticalLowSecurity
    A-002F-BE-004: N+1 Query in dashboardNear-termHighMedBackend
    A-003F-UX-002: Missing ARIA labelsHardeningMedLowFrontend
    A-004F-ARC-001: Monolith service splitLong-termLowHighArch

    Containment Plan (Week 1)

    • A-001 (Critical): Implement input validation middleware on the auth endpoint.
      • Rollback: Revert to commit HEAD^1; existing DB state is unaffected.
      • Observability: Monitor 403 Forbidden spikes in CloudWatch.
      • Acceptance: Snyk scan passes on /api/auth.

    Decision Log (Blockers)

    • D-001: Stakeholder approval needed for A-004 service split due to infrastructure costs.
    • D-002: Confirm if PII data encryption (A-005) requires a maintenance window for backfilling.

    Next steps

    1. Review the full plan at docs/remediation/action-plan.md.
    2. Run plan-to-issues to sync these tasks to GitHub.
    3. Approve the drafted ADRs in docs/remediation/decision-drafts/.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    When a design review or security audit lands on your desk, the gap between "knowing what is wrong" and "knowing what to do on Monday" is a major source of friction. This skill bridge that gap by converting raw findings into a sequenced remediation plan. It moves from immediate containment to long-term hardening, ensuring every critical vulnerability or architectural flaw is mapped to a specific, actionable item.

    What it does

    • Remediation sequencing organizes fixes into containment, near-term, hardening, and long-term phases.
    • Traceability mapping links every finding ID (F-SEC-001) to specific action IDs (A-001) for audit compliance.
    • Risk scoring calculates effort, priority, and impact for every work item.
    • Rollback planning enforces recovery and validation steps for every data migration or system change.
    • Decision logging identifies blockers that require stakeholder sign-off before implementation can start.
    • ADR drafting generates Architectural Decision Records for proposed changes in your repo's specific format.

    How it works

    1. Input ingestion reads your design-review.md and any conflict reports from previous audit stages.
    2. Constraint collection prompts for your specific SLOs, deadlines, capacity, and risk tolerance.
    3. Plan generation invokes the planner to validate findings against code and write the action-plan.md artifact.
    4. Quality gating verifies that every high-severity finding is addressed and every action includes observability and rollback steps.
    5. Issue preparation summarizes the first-week actions and offers to export items to GitHub.

    Frameworks & tools

    Built for environments using GitHub for issue tracking. The automation scripts require Python 3. It integrates with optional companion tools for code mapping and design memory.

    Why this beats prompting it yourself

    Generic prompts often overlook the "how" of a fix, such as rollback procedures or data validation. This skill enforces a strict quality gate that prevents "hand-wavy" remediation, ensuring every task is ready for an engineer to pick up.

    Use cases

    • Post-audit remediation after a security or architectural review.
    • Technical debt reduction by turning a backlog of findings into a structured roadmap.
    • Incident response planning where containment must happen before long-term fixes.

    Known limitations

    Requires Python 3 for bundled scripts. Does not automatically create GitHub issues without the companion plan-to-issues skill. Planning quality depends on the detail in the input review report.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Requires Python 3 for scripts. Does not auto-create GitHub issues without plan-to-issues. Depends on structured findings input.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 12 days ago

    Software
    Python

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Listed12 days ago

    What's inside

    Frequently Asked Questions

    The skill requires a design review or audit report (like a .md or .txt file) and your specific project constraints, such as team capacity, SLOs, and risk tolerance levels.

    Unlike generic prompts, this skill enforces a strict quality gate that requires rollback procedures, observability steps, and Architectural Decision Records (ADRs) for every high-severity fix.

    The skill produces a structured `action-plan.md` artifact; however, the automated export of these tasks into GitHub issues requires the companion `plan-to-issues` skill.

    Yes, you will need a Python 3 environment to run the bundled automation scripts that handle data mapping and constraint collection.

    You receive the core action-planning logic, the Python-based constraint collection scripts, and templates for ADR drafting and traceability mapping.

    The skill is designed to handle various inputs including security audits, architectural reviews, and technical debt backlogs, provided they are in a text-based format.

    New in Agents & Orchestration