What problem does it solve? Teams need a consistent, auditable way to decide whether a reviewed story is ready to ship. This Skill produces a standardized quality gate file that records a clear PASS, CONDITIONAL, or FAIL decision with actionable feedback before code is merged or released. ## Core Features & Use Cases - Structured Gate Decisions: Evaluates stories in REVIEW status against acceptance criteria and outputs PASS, CONDITIONAL, or FAIL with a concise status reason. - Standardized Issue Tracking: Generates issue entries with fixed severity levels (low, medium, high) and prefixed IDs such as SEC-, PERF-, TEST-, and ARCH-. - Strict YAML Schema: Writes gate files to docs/qa/gates/ following a versioned schema with story reference, reviewer, timestamp, top issues, and conditions. - Use Case: After reviewing story 1.3 on user authentication, run the gate to produce docs/qa/gates/1.3-user-auth-login.md documenting a CONDITIONAL pass with a missing rate-limiting issue, then update the story status to DONE. ## Quick Start Run the qa-gate skill to evaluate the reviewed story and generate its quality gate file under docs/qa/gates/.