delivery-immune-conversion

Convert delivery failure evidence into preventive or detective control proposals.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/aurora-atoms/lattice --skill delivery-immune-conversion
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: delivery-immune-conversion
Source: https://github.com/aurora-atoms/lattice/tree/main/skills/delivery-immune-conversion
Command: npx skills add https://github.com/aurora-atoms/lattice --skill delivery-immune-conversion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the gap between learning from delivery failures and implementing sustainable, evidence-based preventive measures, preventing the recurrence of incidents and defects.

Core Features & Use Cases

  • Control Proposal Generation: Automatically structures lessons into test, rule, check, or monitoring proposals.
  • Evidence-Based Governance: Ensures every control is linked to a specific Feature Delivery Case and failure mechanism.
  • Use Case: After an escaped production defect, use this Skill to analyze the failure evidence and generate a validated preflight check or monitoring trigger that prevents similar issues in future deployments.

Quick Start

Use the delivery-immune-conversion skill to analyze the provided failure evidence and generate a control proposal for the current delivery case.

Frequently Asked Questions about delivery-immune-conversion

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

FAQPage Schema
How do I convert post-incident analysis findings into preventive deployment controls?▼

Post-incident analysis findings are converted into preventive controls by applying evidence-based causal analysis to generate bounded test, rule, check, or monitoring proposals that prevent defect recurrence.

What is the best way to structure delivery lessons into actionable governance checks?▼

Delivery lessons are structured into actionable governance checks by linking each control proposal to a specific Feature Delivery Case and failure mechanism, ensuring evidence-based remediation.

How do I generate monitoring triggers from escaped production defect evidence?▼

Monitoring triggers are generated from escaped production defect evidence by analyzing the failure mechanism and creating validated preflight checks that block similar issues in future deployments.

Do I need strict causal evidence to create defect remediation controls?▼

Strict causal evidence is required to create defect remediation controls because the process enforces evidence-based governance and the principle of minimum effective control to ensure sustainable prevention.

Can I use this incident response approach for lifecycle governance within feature delivery workflows?▼

This incident response approach is applicable for lifecycle governance within feature delivery workflows, specifically targeting defect remediation and post-incident analysis to establish bounded detective or preventive controls.

What are the limitations of applying minimum effective control to delivery failure remediation?▼

Applying minimum effective control to delivery failure remediation limits scope to only bounded preventive or detective actions, requiring strict adherence to evidence-based causal analysis rather than broad corrective measures.