Synthesize a structured PRD from conversation context and project files.
npx skills add https://github.com/Davie521/claude-skills --skill to-prd-davie521
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/Davie521/claude-skills/tree/main/plugins/dev-workflow/skills/to-prd Command: npx skills add https://github.com/Davie521/claude-skills --skill to-prd-davie521
Converts fragmented discussion and context into a structured PRD to accelerate product planning and reduce back-and-forth.
Summarize the current conversation and run to-prd to generate and publish a PRD.
High-intent search queries and answers about installing and using this skill.
To generate a PRD from conversation context, the tool synthesizes the current discussion and project details into a structured document covering problem, solution, user stories, and decisions. It automatically structures your fragmented context into a publishable markdown file.
Yes, you can publish a PRD directly to a GitHub issue when the GitHub CLI (gh) is configured. If gh is not configured, you can save the PRD as a markdown file under the docs/prds directory instead.
PRD generation respects existing project context by surfacing CONTEXT.md if present and referencing Architecture Decision Records from docs/adr. This ensures the synthesized output aligns with established project definitions and decisions.
The best way to convert planning session notes into a structured PRD is to summarize the current conversation and run the generation process. It adheres to a standard PRD template to map your notes into problem, solution, scope, and testing sections.
The markdown PRD output includes structured sections for the problem, solution, user stories, decisions, testing, scope, and notes. This ensures the final document covers all necessary product requirements.
No, you do not need the GitHub CLI installed to save a PRD as a markdown file. GitHub CLI is only required if you choose to publish the product requirements document directly as a GitHub issue.
jrjsmrtnAutomate creation of foundational Architecture Decision Records for software projects.
richtaborConvert PRD markdown files into linked GitHub parent and sub-issues.
foolpoet44Translate PRDs into epics, user stories, and acceptance criteria.
MarcoAntoliniConvert conversation context into a Product Requirements Document and integrate it into an issue tracker.
