to-prd-project
This skill writes a PRD and publishes it as a GitHub issue in mattpocock/course-video-manager. It does not apply agent:implement — labeling happens after sub-issues have been created.
Do NOT interview the user — just synthesize what you already know from the conversation. If context is thin, ask the user to talk through the problem first; don't run the skill on an empty plate.
Process
-
Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary (
CONTEXT.md) and respect ADRs underdocs/adr/for areas you're touching. -
Sketch the major modules you'd build or modify. Actively look for opportunities to extract deep modules that can be tested in isolation. A deep module encapsulates a lot of functionality behind a simple, testable interface that rarely changes.
Check with the user that these modules match their expectations and which they want tests written for.
-
Write the PRD using the template below and publish it via
gh issue create. Use a heredoc for the body. Do not applyagent:implement— that's reserved for after sub-issues exist. Add no labels unless the user asks. -
Output the issue URL so the user can pass it to
/to-issues-projectnext.
PRD template
The PRD will be read by: