plan-prd
1
总安装量
1
周安装量
#76957
全站排名
安装命令
npx skills add https://github.com/dthompson-jti/safety-check-app-concept --skill plan-prd
Agent 安装分布
amp
1
cline
1
opencode
1
cursor
1
continue
1
kimi-cli
1
Skill 文档
Plan PRD
Create a comprehensive Product Requirements Document.
When to Use
- Large features or epics
- New user-facing functionality
- Features requiring UX exploration
Artifacts
PRD-[EPIC-NAME].mdindocs/working/task.mdupdated viatask_boundary
Approach
Phase 1: Discovery & Scope
- Proof of Understanding: Summarize core user problem in one sentence.
- User Stories: “As a [user], I want [action], so that [benefit]”
- Non-Goals: Explicitly state out-of-scope items.
Phase 2: Design Options (Forced Diversity)
Generate 4-6 architecturally distinct options varying:
- Information architecture
- Interaction model
- Visual hierarchy
Use Socratic Debate for complex decisions:
- Proponent argues for option
- Adversary critiques
- Synthesis resolves
Phase 3: Detailed UX Specification
State Matrix
| State | Visual | Behavior |
|---|---|---|
| Default | … | … |
| Hover | … | … |
| Focus | … | … |
| Active | … | … |
| Disabled | … | … |
| Empty | … | … |
| Loading | … | … |
| Error | … | … |
ASCII Wireframes
Use var(--token-name) syntax. Reference existing patterns.
Accessibility Requirements
- Keyboard navigation path
- ARIA labels/roles
- Screen reader announcements
- Reduced motion considerations
Phase 4: Validation
- UX Risks & Mitigations table
- Definition of Done checklist
- Reflexion: Hostile Accessibility Auditor critique
Constraints
- No technical architecture â handled in
plan/architecture - All options must consider light/dark mode, accessibility
- Flag as “Hallucination” if using non-existent design tokens