How do I install the Design Prd Writing Team skill?

Run npx skillmds@latest add whyzsm/design-prd-writing-team in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Design Prd Writing Team safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Design Prd Writing Team?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Design Prd Writing Team free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Design Prd Writing Team?

whyzsm (@whyzsm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Design Prd Writing Team by whyzsm — Agent Skill

Name: Design Prd Writing Team
Author: whyzsm

Design Prd Writing Team

End-to-end PRD writing workflow. Use when the user wants a complete product requirements workflow that spans requirement discovery, EPIC/user-story decomposition, prioritization, professional PRD drafting, PRD-to-design handoff, and PRD review/scoring. This skill coordinates the companion skills requirements-analysis, software-manager-skill, prd, prd-writer-pro, prd-to-design-doc, and prd-reviewer.

whyzsm Updated Sep 17, 2026

File contents

Design PRD Writing

Use this skill as the workflow entry point for a complete PRD package. It coordinates the companion skills in this bundle instead of replacing them.

Workflow

Use requirements-analysis to turn the initial idea into structured requirements, stakeholders, dependencies, user stories, and acceptance criteria.
Use software-manager-skill to select frameworks, prioritize requirements with methods such as RICE/MoSCoW/Kano, define MVP scope, and plan product direction.
Use prd to structure implementation-ready PRD items, task lists, user stories, acceptance criteria, and dependency order.
Use prd-writer-pro to produce the polished PRD with background, goals, success metrics, functional requirements, non-functional requirements, edge cases, and launch considerations.
Use prd-to-design-doc when the user needs a design handoff. Convert the PRD into design goals, information architecture, interaction flows, page layout requirements, visual requirements, empty/error states, and delivery checklist.
Use prd-reviewer to score the PRD, identify missing sections, list evidence-based deductions, and propose concrete improvements.

Output Package

When the user asks for a full PRD package, produce these artifacts in order:

Requirement list: structured requirements, users, scenarios, dependencies, user stories, and acceptance criteria.
Prioritization and MVP: scoring table, chosen framework, MVP scope, and deferred scope.
PRD document: professional product requirements document ready for review.
Design requirement document: information architecture, interaction flows, page/layout requirements, and delivery checklist.
Review report: score, module-level deductions, risks, and revision recommendations.

Operating Notes

Ask only the clarifying questions needed to unblock the next step. If the user already gave enough context, move directly into the workflow.
Keep assumptions explicit and mark them as assumptions.
When converting PRD content to design handoff, preserve business rules and acceptance criteria instead of inventing interaction behavior that the PRD does not support.
When reviewing, cite specific PRD sections or missing evidence for every deduction.

---name: design-prd-writing-teamdescription: End-to-end PRD writing workflow. Use when the user wants a complete product requirements workflow that spans requirement discovery, EPIC/user-story decomposition, prioritization, professional PRD drafting, PRD-to-design handoff, and PRD review/scoring. This skill coordinates the companion skills requirements-analysis, software-manager-skill, prd, prd-writer-pro, prd-to-design-doc, and prd-reviewer.---# Design PRD WritingUse this skill as the workflow entry point for a complete PRD package. It coordinates the companion skills in this bundle instead of replacing them.## Workflow1. Use `requirements-analysis` to turn the initial idea into structured requirements, stakeholders, dependencies, user stories, and acceptance criteria.2. Use `software-manager-skill` to select frameworks, prioritize requirements with methods such as RICE/MoSCoW/Kano, define MVP scope, and plan product direction.3. Use `prd` to structure implementation-ready PRD items, task lists, user stories, acceptance criteria, and dependency order.4. Use `prd-writer-pro` to produce the polished PRD with background, goals, success metrics, functional requirements, non-functional requirements, edge cases, and launch considerations.5. Use `prd-to-design-doc` when the user needs a design handoff. Convert the PRD into design goals, information architecture, interaction flows, page layout requirements, visual requirements, empty/error states, and delivery checklist.6. Use `prd-reviewer` to score the PRD, identify missing sections, list evidence-based deductions, and propose concrete improvements.## Output PackageWhen the user asks for a full PRD package, produce these artifacts in order:1. Requirement list: structured requirements, users, scenarios, dependencies, user stories, and acceptance criteria.2. Prioritization and MVP: scoring table, chosen framework, MVP scope, and deferred scope.3. PRD document: professional product requirements document ready for review.4. Design requirement document: information architecture, interaction flows, page/layout requirements, and delivery checklist.5. Review report: score, module-level deductions, risks, and revision recommendations.## Operating Notes- Ask only the clarifying questions needed to unblock the next step. If the user already gave enough context, move directly into the workflow.- Keep assumptions explicit and mark them as assumptions.- When converting PRD content to design handoff, preserve business rules and acceptance criteria instead of inventing interaction behavior that the PRD does not support.- When reviewing, cite specific PRD sections or missing evidence for every deduction.

Frequently asked questions