What problem does it solve? Turning a long design discussion into a formal Product Requirements Document usually means re-interviewing stakeholders and re-writing context from scratch. This Skill converts the current conversation and codebase understanding directly into a structured PRD and files it in the project issue tracker, eliminating redundant interviews. ## Core Features & Use Cases - Context Synthesis: Generates a PRD from the existing conversation and repository exploration, using the project's domain glossary and respecting existing ADRs. - Test Seam Planning: Identifies the highest-level testing seams in the codebase before writing the PRD and confirms them with the user. - Issue Tracker Publishing: Writes the PRD using a fixed template (problem statement, user stories, implementation and testing decisions, scope) and publishes it with the ready-for-agent triage label. - Use Case: After discussing a new feature with an agent, invoke this Skill to produce a complete PRD issue ready for an implementation agent to pick up, without any further triage. ## Quick Start Ask the agent to turn the current conversation into a PRD and publish it to the project issue tracker.