Generate a structured PRD from conversation context, ADRs, and domain glossary.
npx skills add https://github.com/yarma-tech/agent-admin-qonto --skill to-prd-yarma-tech
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/yarma-tech/agent-admin-qonto/tree/main/.agents/skills/to-prd Command: npx skills add https://github.com/yarma-tech/agent-admin-qonto --skill to-prd-yarma-tech
Converts the current conversation context and domain knowledge into a concise, publish-ready PRD, eliminating the need for repeated interviews and handovers.
Provide the current project context and domain glossary, then run the to-prd skill to generate and publish the PRD.
High-intent search queries and answers about installing and using this skill.
To generate a PRD from existing context and ADRs, provide your conversation context and domain glossary, and the skill synthesizes them into a structured, publish-ready PRD template with recommended modules and publishing steps.
The best way to turn conversation context into a production-ready PRD is to synthesize domain knowledge and ADRs into a concise document, eliminating repeated interviews and handovers while adhering to project vocabulary for issue-tracker publishing.
Yes, you can update a PRD as your project context evolves by running the skill again to support iterative refinements, ensuring the synthesized document reflects the latest domain glossary and conversation context.
Yes, generating a PRD this way includes triage-ready labels for issue tracking when provided, allowing you to publish the structured document directly to the project issue tracker with appropriate triage metadata.
Yes, you need a domain glossary to create a structured PRD template, because the skill uses it alongside ADRs and conversation context to ensure the generated document adheres to specific project vocabulary.
You use ADRs when synthesizing a PRD for issue-tracker publishing to ensure the generated document respects architectural decisions and project constraints, producing a structured template aligned with established technical directions.
ZzAveGenerate a PRD from conversation context and codebase understanding, then publish it to the issue tracker.
az9713Generate a PRD from conversation context and publish it to the issue tracker.
jonkraatzGenerate a Product Requirements Document from discussion context and publish it to the issue tracker.
liuwenji007Analyze unstructured business requirements into structured documents and actionable todolists.
