Synthesizes conversation context into a structured PRD file for project planning.
Install
mkdir -p .claude/skills/to-prd && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13867" && unzip -o skill.zip -d .claude/skills/to-prd && rm skill.zipInstalls to .claude/skills/to-prd
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Turn the current conversation context into a PRD and save it to wiki/llm_conversations/. Use when user wants to create a PRD from the current context.Key capabilities
- →Synthesize conversation context into a PRD
- →Sketch major modules or schema changes
- →Write problem statements for PRDs
- →Create user stories for PRDs
- →Document implementation decisions in PRDs
How it works
The skill synthesizes the current conversation context into a PRD document, following a predefined template and saving it to a specified directory.
Inputs & outputs
When to use to-prd
- →Create a PRD from brainstorming
- →Document feature requirements
- →Save project requirements to wiki
About this skill
This skill takes the current conversation context and produces a PRD. Do NOT interview the user — just synthesize what you already know.
Process
-
Sketch out the major modules or schema changes needed. Check with the user that these match expectations.
-
Write the PRD using the template below, then save it to
wiki/llm_conversations/YYYY-MM-DD-<feature-slug>.md.
Problem Statement
The problem that the user is facing, from the user's perspective.
Solution
The solution to the problem, from the user's perspective.
User Stories
A numbered list of user stories in the format:
- As a <actor>, I want <feature>, so that <benefit>
Implementation Decisions
- Schema changes or new page types
- Operational changes to AGENT.md
- Skill or command changes
Out of Scope
What is explicitly not covered by this PRD.
Further Notes
Any additional context.
</prd-template>When not to use it
- →When the user wants to be interviewed for PRD content
Limitations
- →The skill does not interview the user for PRD content, it synthesizes what is already known.
- →The skill saves the PRD to a specific directory: wiki/llm_conversations/.
- →The skill requires the user to confirm major modules or schema changes.
How it compares
This skill automatically generates a structured PRD from existing conversation context, contrasting with a manual process of drafting a PRD from scratch.
Compared to similar skills
to-prd side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| to-prd (this skill) | 0 | 3mo | No flags | Beginner |
| getting-started-guide | 1 | 8mo | No flags | Beginner |
| planning-with-files | 233 | 6mo | Review | Intermediate |
| launch-strategy | 4 | 6mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by 0r1xByte
View all by 0r1xByte →You might also like
getting-started-guide
Microck
当用户开始新小说项目时激活 - 通过温和的提示和解释引导他们完成七步方法论（constitution → specify → clarify → plan → tasks → write → analyze）
planning-with-files
davila7
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
launch-strategy
davila7
When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.
product-requirements
cexll
Interactive Product Owner skill for requirements gathering, analysis, and PRD generation. Triggers when users request product requirements, feature specification, PRD creation, or need help understanding and documenting project requirements. Uses quality scoring and iterative dialogue to ensure comprehensive requirements before generating professional PRD documents.
ticket-manager
galz10
Expertise in managing Linear tickets locally using Markdown files. Use when you need to create, update, search, or break down features into atomic implementation tickets.
prd-drafter
galz10
Pickle Rick's PRD Engine. Use when you need to define the requirements, scope, and goals for a new feature or project before coding to avoid "Jerry-work."