to-prdlisted

Synthesize the current conversation context into a PRD. Do not ask discovery questions — if something is unclear, state your assumption. Do confirm technical choices (seams, contracts) with the user before writing the final document. Issues live as local markdown files — see `docs/agents/issue-tracker.md` for the file layout and `docs/agents/triage-labels.md` for valid status strings. ## Process 1. **Determine the feature slug** before anything else: - If the user provided a slug or path argument, extract it from there. - Otherwise, list existing directories under `.scratch/` and pick the one that clearly matches the topic. - If no match is found, ask: "What feature slug should I use? (This becomes the `.scratch/<slug>/` directory.)" Never guess the slug silently — confirm with the user if there's any ambiguity. 2. Explore the repo to understand the current state of the codebase, if you haven't already. Also check for `.scratch/<feature-slug>/decisions.md` — if it exists, read it and use the resolved decisions as primary input. Use the project's domain glossary vocabulary throughout, and respect any ADRs in the area you're touching. 3. Sketch the seams at which the feature will be tested. Prefer existing seams over new ones; prefer the highest seam possible. Present these to the user for confirmation before writing. 4. Write the PRD using the template below, then save it to `.scratch/<feature-slug>/PRD.md` (creating the directory if needed). **Security**: