What problem does it solve? When a bug is found in production after a spec has already been merged, or a small improvement arrives with no originating spec, running the full PRD/TRD pipeline is overkill — but skipping rigor entirely is unacceptable. This Skill formalizes a lightweight hotfix path that keeps TDD, code review, and the relevant quality gates without generating product or architecture documents. ## Core Features & Use Cases - Scoped hotfix workflow: Creates a hotfix/<slug> or fix/<slug> branch from main, requires a GitHub issue before any branch exists, and opens a draft PR referencing it with Closes #N. - Objective review criteria: Code review always runs; QA runs when an acceptance criterion exists; security runs when the diff touches auth, sessions, or sensitive data; SRE runs only on infrastructure, CI/CD, or dependency changes. - In-place artifact updates: Review artifacts (code-review.md, qa-report.md, etc.) are edited in the related spec directory with a hotfix-<date> history line, or in a dedicated spec directory when no origin spec exists. - Use Case: A production login bug is reported two weeks after its feature shipped. Use this Skill to create the issue, branch, failing test, fix, and run code review plus security review — all recorded against the original spec. ## Quick Start Use the sdd-hotfix skill to fix the production bug where session tokens expire prematurely, starting from a GitHub issue and following TDD.
