What problem does it solve? Formal checklist gates can pass a story that still references unread skills, superseded ADRs, dead commits, or corrupted database fields. This Skill enforces substantive verification of a story record before it is marked ready-for-dev, catching iteration pollution, cross-story file conflicts, and self-write corruption that surface only later during development. ## Core Features & Use Cases - Seven depth gates (D1-D7): Verifies required skills were actually read, cross-references ADR/IDD versions and forbidden changes, traces PRD requirement sources, live-reverifies UI stories via Chrome MCP, detects stale file/commit references, checks sibling-story file conflicts, and validates written DB field integrity. - WARN-as-BLOCK policy: Warnings default to blocking (exit 2) unless explicitly accepted with a reason via --accept-warn, preventing silent accumulation of unresolved issues. - Use Case: Before upserting a newly created story into the SQLite context database, run the gate script against the story ID to receive a markdown report of PASS/WARN/BLOCK per gate, with findings appended to the story's dev_notes. ## Quick Start Run the depth gate on my story by executing node .claude/skills/phycool-create-story-depth-gate/scripts/run-depth-gate.js with the story ID and show me the report.
