What problem does it solve? Turning a long planning 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 issue tracker, without re-interviewing the user. ## Core Features & Use Cases - Context Synthesis: Converts the current conversation and repository exploration into a structured PRD covering problem statement, solution, user stories, implementation decisions, testing decisions, and scope. - Test Seam Planning: Identifies existing architectural seams for testing before writing the PRD and confirms them with the user. - Issue Tracker Publishing: Publishes the finished PRD to GitHub or Linear via MCP and applies the ready-for-agent triage label. - Use Case: After discussing a new seat-locking feature for a ticketing app, ask the agent to produce a PRD; it explores the codebase, drafts extensive user stories, and posts the PRD as a GitHub issue ready for an implementation agent. ## Quick Start Ask the agent to turn the current conversation into a PRD and publish it to the project issue tracker.