What problem does it solve? Writing tech-debt documentation often produces vague, assumption-based write-ups that engineers cannot act on. This Skill guides the creation of tech-debt plan documents for the mahjong-site project that cite real files, line numbers, and code snippets, conforming to the format expected by the execute-tech-debt-plan workflow. ## Core Features & Use Cases - Code-grounded discovery: Uses Grep, Glob, and Read to locate affected files and line numbers before writing, so every Problem Details entry cites actual evidence. - Structured template: Fills a fixed template with Title, State, Summary, Problem Details, Impact, Suggested Fix, and Related Files sections. - Area classification: Routes the document into the correct docs/tech-debt/ subdirectory (auth, games, tournaments, users, ranked-league, resources, ui, or a new folder). - Use Case: You notice a race condition in game verification. Describe it in one sentence, and the Skill explores the relevant code, drafts a complete plan document, and writes it to docs/tech-debt/games/game-verification-race-condition.md. ## Quick Start Ask the assistant to write a tech-debt plan for a specific bug or UX gap, providing a one-sentence description of the problem.
