amadeus-security-patch

Run the AI-DLC security-patch workflow for CVE remediation and patch planning.

5|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/amadeus-dlc/amadeus --skill amadeus-security-patch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amadeus-security-patch
Source: https://github.com/amadeus-dlc/amadeus/tree/main/.agents/skills/amadeus-security-patch
Command: npx skills add https://github.com/amadeus-dlc/amadeus --skill amadeus-security-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates scope detection and manual routing for security patch work by locking the AI-DLC workflow to the security-patch scope from the start.

Core Features & Use Cases

  • Fixed-Scope Orchestration: Runs the full AI-DLC loop with security-patch baked in, so reruns resume the same workflow deterministically.
  • CVE Response: Supports vulnerability remediation, patch planning, and stage-by-stage execution for urgent security work.
  • Protocol-Guided Interaction: Follows engine directives for stage execution, questions, reports, and completion handoff.

Quick Start

Ask the skill to run the security-patch workflow for your current workspace and continue until the engine reports completion.

Frequently Asked Questions about amadeus-security-patch

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

FAQPage Schema
How do I orchestrate a fixed-scope workflow for CVE response?

A fixed-scope CVE response workflow eliminates scope detection by locking the AI-DLC engine to the security-patch scope from the start. It supports vulnerability remediation, patch planning, and stage-by-stage execution for urgent security work.

What is the best way to handle security patch planning without manual scope detection?

Fixed-scope orchestration bakes the security-patch scope into the AI-DLC workflow, ensuring deterministic stage routing. It handles security incident triage, patch planning, and completion handoff without manual scope detection.

Can I resume a vulnerability remediation workflow if the execution is interrupted?

Yes, reruns resume the same workflow deterministically because the security-patch scope is baked into the AI-DLC loop. This prevents scope detection drift and allows continued stage execution after interruption.

Does the security patch workflow require an existing AI-DLC workspace?

Yes, this fixed-scope CVE response workflow requires an existing AI-DLC workspace to operate. It applies deterministic stage routing, report round-trips, and grill-bridge question handling within that established environment.

When do I need deterministic stage routing for security incident triage?

You need deterministic stage routing for security incident triage when handling urgent CVE remediation. It enforces protocol-guided stage execution, report round-trips, and completion handoff without scope detection.