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, teams need a lightweight path that skips PRD/TRD creation without skipping rigor. This Skill formalizes that post-merge correction flow inside an SDD pipeline. ## Core Features & Use Cases - Scoped correction workflow: Handles post-merge bugs and small spec-less improvements without generating PRD or TRD documents, while keeping TDD and code review mandatory. - Objective review criteria: Decides which reviews run (code review always; QA, security, and SRE based on explicit criteria) and records skipped reviews with standardized headings. - GitHub issue gate: Requires a confirmed or newly created GitHub issue (with milestone or spec label linkage) before any branch is created. - Use Case: A production bug is reported in a feature whose spec was merged last week. Use this Skill to create the issue, branch from main, implement the fix with TDD, run code review plus applicable reviews, and record everything in the related spec's artifacts. ## Quick Start Use the hotfix skill to fix the production login timeout bug reported after the auth spec was merged, creating the GitHub issue and running the applicable reviews.