Before generating any content, check aico.json in project root for language field to determine the output language. If not set, default to English.
Process
Gather context: Check docs/reference/pm/ for existing product context
Define problem & solution: Start with clear problem statement and high-level solution
Set boundaries: Clearly separate Goals from Non-Goals
Document requirements: List functional requirements (FR-XXX format)
Define success: Set measurable success criteria
Track unknowns: Document open questions for later clarification
Save PRD: ALWAYS write to docs/reference/pm/versions/{version-name}.md
PRD Template
# [Feature Name] PRD
> Project: [project-name]
> Created: YYYY-MM-DD
> Last Updated: YYYY-MM-DD
## 1. Overview
- Problem statement
- Proposed solution (high-level)
- Success metrics
## 2. Background
- Current state
- User pain points
- Market context (if relevant)
## 3. Goals & Non-Goals
### Goals
- What this feature WILL accomplish
### Non-Goals
- What this feature will NOT address
## 4. User Stories
[Link to or embed user stories]
## 5. Functional Requirements
- FR-001: [Requirement description]
- FR-002: [Requirement description]
## 6. User Experience
- Key user flows
- Interaction patterns
- Edge cases
## 7. Success Criteria
- Measurable outcomes
- Acceptance criteria
## 8. Open Questions
- Unresolved decisions
- Items needing clarification
Key Rules
ALWAYS focus on WHAT to build, NOT HOW to implement
MUST include quantifiable success metrics
ALWAYS explicitly state what's out of scope in Non-Goals
MUST save output to docs/reference/pm/versions/ directory
Common Mistakes
❌ Include implementation details → ✅ Focus on WHAT, not HOW
❌ Vague success metrics → ✅ Quantifiable outcomes
❌ Missing non-goals → ✅ Explicitly state what's out of scope
Iron Law
NO PRD WITHOUT VALIDATED REQUIREMENTS
This rule is non-negotiable. Before writing PRD:
User pain points must be documented
Success metrics must be defined
Scope must be explicitly approved by user
Rationalization Defense
Excuse
Reality
"Requirements are clear enough"
Implicit requirements cause scope creep
"We can refine the PRD later"
Late changes cost 10x more to implement
"User will accept anything"
Users always have hidden expectations
"It's just a small feature"
Small features grow into big problems
1---2name: aico-pm-prd-writing-23description: Aico Pm Prd Writing4---56# PRD Writing78## Language Configuration910Before generating any content, check `aico.json` in project root for `language` field to determine the output language. If not set, default to English.1112## Process13141. **Gather context**: Check `docs/reference/pm/` for existing product context152. **Define problem & solution**: Start with clear problem statement and high-level solution163. **Set boundaries**: Clearly separate Goals from Non-Goals174. **Document requirements**: List functional requirements (FR-XXX format)185. **Define success**: Set measurable success criteria196. **Track unknowns**: Document open questions for later clarification207. **Save PRD**: ALWAYS write to `docs/reference/pm/versions/{version-name}.md`2122## PRD Template2324```markdown25# [Feature Name] PRD2627> Project: [project-name]28> Created: YYYY-MM-DD29> Last Updated: YYYY-MM-DD3031## 1. Overview3233- Problem statement34- Proposed solution (high-level)35- Success metrics3637## 2. Background3839- Current state40- User pain points41- Market context (if relevant)4243## 3. Goals & Non-Goals4445### Goals4647- What this feature WILL accomplish4849### Non-Goals5051- What this feature will NOT address5253## 4. User Stories5455[Link to or embed user stories]5657## 5. Functional Requirements5859- FR-001: [Requirement description]60- FR-002: [Requirement description]6162## 6. User Experience6364- Key user flows65- Interaction patterns66- Edge cases6768## 7. Success Criteria6970- Measurable outcomes71- Acceptance criteria7273## 8. Open Questions7475- Unresolved decisions76- Items needing clarification77```7879## Key Rules8081- ALWAYS focus on WHAT to build, NOT HOW to implement82- MUST include quantifiable success metrics83- ALWAYS explicitly state what's out of scope in Non-Goals84- MUST save output to `docs/reference/pm/versions/` directory8586## Common Mistakes8788- ❌ Include implementation details → ✅ Focus on WHAT, not HOW89- ❌ Vague success metrics → ✅ Quantifiable outcomes90- ❌ Missing non-goals → ✅ Explicitly state what's out of scope9192---9394## Iron Law9596**NO PRD WITHOUT VALIDATED REQUIREMENTS**9798This rule is non-negotiable. Before writing PRD:991001. User pain points must be documented1012. Success metrics must be defined1023. Scope must be explicitly approved by user103104### Rationalization Defense105106| Excuse | Reality |107| ------------------------------- | --------------------------------------- |108| "Requirements are clear enough" | Implicit requirements cause scope creep |109| "We can refine the PRD later" | Late changes cost 10x more to implement |110| "User will accept anything" | Users always have hidden expectations |111| "It's just a small feature" | Small features grow into big problems |
Run npx skillmds@latest add majiayu000/aico-pm-prd-writing-2 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.
Aico Pm Prd Writing It is listed under Product & Planning on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
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.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.
majiayu000