Generate a product requirements document from conversation context and repository understanding.
npx skills add https://github.com/shushuzn/Rairos --skill to-prd-shushuzn
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/shushuzn/Rairos/tree/main/skills/to-prd Command: npx skills add https://github.com/shushuzn/Rairos --skill to-prd-shushuzn
It helps you convert a messy set of discussion notes, requirements, and existing codebase context into a clear, actionable Product Requirements Document (PRD) that can be shared and triaged in the project issue tracker.
ready-for-agent.Ask to convert the current discussion into a PRD and publish it to the project issue tracker using the ready-for-agent label.
High-intent search queries and answers about installing and using this skill.
To generate a product requirements document, the Skill synthesizes current conversation context and existing repository understanding into actionable scope, user stories, and testing strategy without requiring manual follow-up questions.
PRD generation leverages the project's domain glossary vocabulary and relevant architecture decision records to ensure the proposed feature requirements reflect how the codebase works today.
Yes, the Skill publishes the completed product requirements document directly to the project issue tracker, applying the expected triage label vocabulary and setting the issue status to ready-for-agent.
The best way to formalize ambiguous ideas is to process the discussion notes through a PRD template, which outputs structured user stories, clear scope boundaries, and a defined testing plan.
Yes, defining out-of-scope boundaries is a core requirement of the generated product requirements document, ensuring teams establish clear limitations and prevent scope creep before triaging.
PRD synthesis works by directly converting the available discussion context into a complete document, operating without asking follow-up questions to fill in missing requirement gaps.
ricardoalt1515Generate a Product Requirements Document from conversation context and codebase understanding.
FlowmGenerate a PRD from product discussion context and publish it to the issue tracker.
babuallyGenerate a structured PRD from conversation and repository context.
hulusi-tuncPlan accessibility testing strategies with automated, manual, and user testing.