Convert conversation context into a structured PRD and publish it to the issue tracker.
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill to-prd-ayehiaa
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.claude/skills/to-prd Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill to-prd-ayehiaa
It helps convert a conversation and existing project understanding into a structured PRD so teams can quickly align on scope, requirements, and next steps.
Run the to-prd skill to generate and publish a PRD based on the current conversation context using the repo’s glossary vocabulary and the issue tracker’s triage label conventions.
High-intent search queries and answers about installing and using this skill.
Generating a PRD from conversation context involves synthesizing existing project discussions and repository knowledge into a structured product requirements document without requiring additional user interviews.
A product requirements document for implementation readiness should include sections for problem definition, solution, extensive user stories, implementation decisions, testing decisions, out-of-scope items, and further notes.
Publishing a PRD to an issue tracker requires applying the project's specific ready-for-agent triage label conventions before submitting the structured requirements document directly from the synthesized conversation context.
Generating product requirements from repo knowledge does require repo exploration to identify deep modules and extract glossary-aligned terminology, ensuring the PRD accurately reflects existing project architecture and vocabulary.
Creating user stories for module planning without manual stakeholder interviews is possible by converting current conversation context and existing repository understanding directly into structured implementation and testing decisions.
Aligning team scope and requirements from a feature definition discussion is best achieved by converting the context into a structured PRD that documents implementation and testing decisions using the repository's standard glossary vocabulary.
nikbrunnerExtract and formalize domain terminology from conversations into GLOSSARY.md.
mostafa-K-raihanConfigure per-repo Agent skills settings for GitHub or local markdown issue trackers.
Lev-itCreates a Product Requirements Document from conversation and codebase understanding and publishes it to the issue tracker.
nselugaGenerate a Product Requirements Document from conversation context and publish it to the issue tracker.
