write-a-prd
This skill will be invoked when the user wants to create a PRD.
-
Ask the user for a concise but clear description of the problem they want to solve, the outcome they want, who it is for, and any initial ideas for solutions.
-
Reuse the discussion already present in the current thread.
If the problem, constraints, and key decisions have already been clarified earlier in the conversation, do not repeat the same interview. Only ask follow-up questions for unresolved, ambiguous, or conflicting points.
- Explore the repo to verify their assertions and understand the current state of the codebase when relevant.
Use repo findings to answer factual questions yourself instead of asking the user unnecessarily. Call out existing behavior, terminology, and constraints that materially affect the PRD.
- Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Make sure the discussion covers the complete feature surface, including:
More from sones3/skills
prd-to-issues
Break a PRD into independent GitHub issues, with backend-first then frontend-linked workflow. Each issue is fully discussed before implementation. Use when converting a PRD to actionable work items.
14grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
13ubiquitous-language
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
12start-next-issue
Suggests the next GitHub issue to work on from a PRD breakdown, confirms it with the user, and initiates the pre-implementation discussion.
11discuss-in-french
Ensures that discussions with the user are conducted in French, but all deliverables, documentation, and implementation outputs are written in English.
10start-implementation
Implements a GitHub issue continuously until finished, documents the work and recommendations, commits, and closes the issue. Confirms the issue with the user only if it is not already in context.
9