# Issue tracker: Local Markdown Issues and specs (you may know a spec as a PRD) for this repo live as markdown files in `.scratch/`. ## Conventions - One feature per directory: `.scratch//` - The spec is `.scratch//spec.md` - Implementation issues are one file per ticket at `.scratch//issues/-.md`, numbered from `01` - never a single combined tickets file - Triage state is recorded as a `Status:` line near the top of each issue file - Comments and conversation history append to the bottom of the file under a `## Comments` heading ## When a skill says "publish to the issue tracker" Create a new file under `.scratch//` (creating the directory if needed). ## When a skill says "fetch the relevant ticket" Read the file at the referenced path. The user will normally pass the path or the issue number directly.