Generate a one-page product spec from DESIGN.md briefs.
npx skills add https://github.com/az9713/open-design-tutorial --skill pm-spec-az9713
Please help me install this Agent Skill. Skill: pm-spec Source: https://github.com/az9713/open-design-tutorial/tree/main/skills/pm-spec Command: npx skills add https://github.com/az9713/open-design-tutorial --skill pm-spec-az9713
Product teams often need a concise, single-page PRD to align design, engineering, and product stakeholders from ideation to rollout.
Read the active DESIGN.md and generate a one-page PRD with sections for problem, goals, scope, user stories, milestones, and open questions.
High-intent search queries and answers about installing and using this skill.
To generate a one-page product spec, the Skill extracts the problem, goals, scope, user stories, milestones, and open questions from your design brief and outputs a standardized, concise PRD artifact.
A concise PRD for stakeholder alignment should include a header with title, status, date, and owner, a three-line summary, and separated sections for problem, goals, scope, user stories, milestones, and open questions.
Yes, you can create a standardized PRD by reading your active DESIGN.md file; the Skill processes design notes and rollout plans to produce a consistent, single-page product spec.
This PRD generation approach works for planning sessions and design reviews by enforcing a consistent structure that captures problem, goals, scope, user stories, rollout plans, and open questions for team reuse.
The best way to document user stories and open questions is extracting them directly from design briefs into a standardized one-page product spec, maintaining clear separation for quick stakeholder reference.
pipixia-labsConvert a design brief into a structured one-page product spec.
dennywu2966Generate a structured PRD from a feature description with clarifying questions.
clearclownGenerate design.md and task plans from requirements using spec-driven development.
kevinlinGenerate a structured PRD with problem statements, goals, user stories, and acceptance criteria.
