What problem does it solve? Turning a long design conversation into a structured Product Requirements Document is tedious and error-prone. This Skill synthesizes the existing conversation context and codebase understanding into a complete PRD and publishes it directly to the project's issue tracker, without re-interviewing the user. ## Core Features & Use Cases - Context Synthesis: Converts the current conversation and codebase exploration into a structured PRD covering problem statement, solution, user stories, implementation decisions, testing decisions, and scope. - Test Seam Planning: Identifies existing or proposed testing seams in the codebase and confirms them with the user before writing the PRD. - Issue Tracker Publishing: Publishes the finished PRD to the project issue tracker and applies the ready-for-agent triage label. - Use Case: After brainstorming a new feature with the agent, ask it to produce a PRD. It explores the repo, respects the domain glossary and ADRs, drafts the PRD from the template, and files it as a triaged issue. ## Quick Start Turn everything we have discussed so far into a PRD and publish it to the issue tracker.