Generate a formal PRD from conversation context and codebase exploration.
npx skills add https://github.com/vessux/dotfiles --skill to-prd-vessux
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/vessux/dotfiles/tree/main/umbel/skills/pocock/to-prd Command: npx skills add https://github.com/vessux/dotfiles --skill to-prd-vessux
Turning conversations and scattered context into a structured Product Requirements Document (PRD) that can be shared, reviewed, and tracked in the project issue tracker.
Ask the AI to convert 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 PRD from conversation context, the Skill transforms stakeholder discussions and codebase exploration into a formal document with problem statements, scope, and success metrics. It maps requirements and acceptance criteria directly from the current context.
Yes, you can publish a product requirements document to an issue tracker. The Skill creates or updates an issue with metadata and references, ensuring the generated PRD integrates directly into your project's existing issue tracker workflow.
Converting project requirements into a formal PRD generates sections for the problem statement, proposed solution, scope, success metrics, and assumptions. It extracts key goals and constraints from discussions to form a complete document.
Generating PRD documentation requires clear mapping of acceptance criteria, success metrics, scope, and publication steps. The Skill ensures these elements are explicitly defined from the conversation context before finalizing the document.
The best way to turn scattered stakeholder discussions into structured product management documentation is by applying an automated workflow. This Skill extracts goals and constraints from conversations, formalizing them into a tracked PRD ready for review.
You should not use automated PRD generation when your product planning workflows lack clear stakeholder discussions or codebase context. The Skill requires explicit conversation context and project understanding to accurately map requirements and publication steps.
FlowmGenerate a PRD from product discussion context and publish it to the issue tracker.
oxieBreak down implementation plans into 20-30 testable tasks with acceptance criteria.
wzserCategorize issues and transition states within a project's issue tracker.
GustavoGutierrezGenerate Gherkin Given/When/Then acceptance criteria from user stories.
