Convert conversation context and codebase understanding into a structured PRD.
npx skills add https://github.com/kartikkabadi/skills --skill to-prd-kartikkabadi
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/kartikkabadi/skills/tree/main/to-prd Command: npx skills add https://github.com/kartikkabadi/skills --skill to-prd-kartikkabadi
This Skill helps turn an existing conversation and codebase understanding into a structured product requirements document without starting from scratch. It is useful when a product or engineering task needs to be captured clearly enough to publish, review, and track in an issue system.
Ask the assistant to turn the current conversation context into a PRD and publish it to the project issue tracker.
High-intent search queries and answers about installing and using this skill.
To generate a product requirements document from conversation context, the Skill synthesizes existing discussion and codebase understanding into a structured PRD. This includes problem statements, user stories, implementation decisions, and testing decisions ready for review.
Preparing a PRD for development handoff involves structuring the document with problem statements, user stories, and testing decisions, then applying the required triage label. This ensures the feature planning output is ready to publish directly to the project issue tracker.
Yes, generating user stories and implementation decisions from an existing discussion is the core function. The Skill extracts synthesis of existing context to produce extensive user stories and implementation decisions required for a complete and publishable PRD.
Generating a PRD requires no specific issue tracker setup, as it focuses on synthesizing context into a structured document. It then prepares the output for publication to the project issue tracker and applies the necessary triage label.
The best way to structure a PRD for feature planning is to divide it into problem statement, solution, user stories, implementation decisions, testing decisions, and out of scope sections. This structure captures the context clearly enough for downstream execution.
JuanMS20Generate a Product Requirements Document from conversation context and codebase understanding.
amazingloft999-droidCreates a PRD from conversation context and publishes it to the issue tracker.
ian-pascoeConvert conversation and codebase context into a structured PRD.
mmartinsolivConvert conversation and repository context into a publishable product requirements document.
