Generate product requirements documents from prompts and project context.
npx skills add https://github.com/mshadmanrahman/pm-pilot --skill prd-mshadmanrahman
Please help me install this Agent Skill. Skill: prd Source: https://github.com/mshadmanrahman/pm-pilot/tree/main/skills/pm-core/prd Command: npx skills add https://github.com/mshadmanrahman/pm-pilot --skill prd-mshadmanrahman
Product teams and stakeholders often need clear, appropriately scoped requirements documents quickly, but struggle to pick the right depth, capture assumptions, and convert raw research or notes into buildable requirements. This Skill standardizes the process of turning prompts, meeting notes, and existing context into one-pagers, briefs, full PRDs, or RFCs so decisions and execution move faster.
Draft a full PRD for [feature name] including problem, user stories, acceptance criteria, metrics, rollout plan, and open questions.
High-intent search queries and answers about installing and using this skill.
To generate a product requirements document, provide your meeting notes and prompts so the system can auto-detect depth, cross-reference context, and output structured requirements with acceptance criteria and rollout plans.
The difference lies in document depth: a one-pager or brief summarizes core requirements, while a full PRD details rollout and metrics, and an RFC structures engineering decision workflows for discovery and design.
Write acceptance criteria and rollout plans by inputting your feature prompt; the system structures the product spec to automatically include P0 criteria, metrics, risks, open questions, and phased rollout guidance.
Yes, you can use raw research links to draft build-ready product management documents because the system reads referenced research, tags assumptions, and converts notes into structured user stories and requirements.
Use an RFC instead of a full PRD when your feature discovery requires engineering decision workflows and design validation rather than structured rollout plans and acceptance criteria.
The best way to structure open questions and assumptions in a PRD is to let the system automatically tag them from your raw prompts, cross-reference available project context, and suggest prioritized next steps.
PixoraftGenerate show notes, blogs, newsletters, social posts, quote cards, and video clips from podcast transcripts.
mtsatryanDefine product strategy and market research plans to align development with business goals.
rchandnaWUSTLParse RFCs and design documents into structured Markdown with metadata.
i-standard1Generate requirements documents from natural language prompts using project templates.