sdd-hotfix

Guide SDD hotfix triage, minimal spec creation, implementation, and verification.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/javierhbr/random-poc --skill sdd-hotfix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-hotfix
Source: https://github.com/javierhbr/random-poc/tree/main/sdd-mcp/sdd-mcp/mnt/user-data/outputs/sdd-agent/skills/sdd-hotfix
Command: npx skills add https://github.com/javierhbr/random-poc --skill sdd-hotfix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides users through the process of quickly and safely resolving production incidents or critical bugs within the Spec-Driven Development (SDD) framework, ensuring traceability is maintained even under pressure.

Core Features & Use Cases

  • Incident Triage: Helps determine if a hotfix is component-only, contract-changing, or policy-violating to route it correctly.
  • Minimal Spec Creation: Facilitates the rapid creation of essential Hotfix Specs or Bug Specs.
  • Guided Implementation & Verification: Provides steps for implementing the fix and verifying its success.
  • Follow-up Spec Enforcement: Mandates the creation of a comprehensive follow-up spec to prevent recurrence and document decisions.
  • Use Case: A critical payment processing API is failing in production. This Skill helps the on-call engineer quickly create a Hotfix Spec, implement the minimal change, verify the fix, and ensures a follow-up spec is created in the next sprint to harden the system.

Quick Start

Use the sdd-hotfix skill to guide me through resolving a production incident affecting the user authentication service.

Frequently Asked Questions about sdd-hotfix

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

FAQPage Schema
How do I resolve a production incident while maintaining spec-driven development traceability?▼

To resolve a production incident with traceability, follow the SDD hotfix process: triage the incident, create a minimal hotfix spec, implement the fix, verify it, and mandate a follow-up spec for long-term system health.

What is the best way to triage a critical bug before deploying a hotfix?▼

The best way to triage a critical bug is to determine if the hotfix is component-only, contract-changing, or policy-violating, which routes the incident correctly and dictates the required specification and implementation steps.

How do I create a minimal hotfix spec for a failing payment processing API?▼

To create a minimal hotfix spec for a failing API, use a guided bug resolution process to document only the essential changes needed to stop the production failure, ensuring speed without losing system traceability.

Why do I need a follow-up spec after deploying an emergency hotfix?▼

You need a follow-up spec after deploying an emergency hotfix to prevent incident recurrence, document temporary decisions made under pressure, and harden the system for long-term health in the next sprint.

Does this incident response process handle policy-violating production scenarios?▼

Yes, this incident response process explicitly handles policy-violating production scenarios, alongside component-only and contract-changing incidents, routing them correctly to ensure proper resolution and documentation.