Generate a Product Requirements Document from conversation, codebase, and research.
npx skills add https://github.com/dformoso/positronic --skill to-prd-dformoso
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/dformoso/positronic/tree/main/skills/defining/to-prd Command: npx skills add https://github.com/dformoso/positronic --skill to-prd-dformoso
This Skill helps create a Product Requirements Document (PRD) from the current conversation context, codebase understanding, and relevant research, providing a structured outline for what and why the product should be built.
Run the to-prd skill to generate a PRD based on the current conversation context.
High-intent search queries and answers about installing and using this skill.
Generating a Product Requirements Document from existing context involves synthesizing user conversations, codebase understanding, and research findings to construct a structured PRD. This process automates requirement engineering by extracting problem statements, target users, and goals directly from available project context.
A comprehensive PRD for product development should include sections for problem statement, target user, goals, solution overview, user journeys, non-goals, out of scope, functional requirements, risks, and open questions. These components ensure structured context synthesis and clear project planning boundaries.
Yes, amending an existing PRD with scoped changes is supported through Amend Mode. This allows targeted edits to specific functional requirements or user journeys without regenerating the entire document, preserving existing context synthesis while updating only designated sections.
PRD generation works directly with codebase analysis and research summaries by incorporating these inputs into the document structure. It analyzes codebase details and research findings alongside user conversations to inform solution overviews and functional requirements.
Formalizing project planning into a PRD format is needed when transitioning from exploratory conversations and research to structured product development. It captures requirement engineering decisions and establishes clear non-goals and open questions before implementation begins.
arugo11Analyze codebases with agent teams to generate project briefs and implementation plans.
clovernguyen1010-ship-itGenerate a structured BMAD PRD with verifiable requirements from user input.
alex-tgkCalculate RICE scores, analyze customer interviews, and generate PRDs from templates.
rohunjGenerate structured PRDs from feature prompts with clarifying questions.
