---
name: create-new-product-design
description: New product design work standard. Use when the user needs to design a brand new product from scratch, covering strategy, scope, structure, and presentation layers step by step.
---

# Create New Product Design

Complete product design deliverables step by step. **Each deliverable MUST be confirmed by the user before proceeding to the next step.**

## Working Principles
- Pause after each deliverable and wait for user confirmation before continuing
- All design decisions MUST strictly follow the Product Strategy document; any deviation is an error
- Follow the minimum viable principle: if not necessary, do not add

## File Organization

**Before producing any output**, MUST first create the following folder structure in the project root (skip if already exists):

```
PRD/
├── 1-Strategy/
├── 2-Scope/
├── 3-Structure/
└── 4-Presentation/
```

All output documents MUST be saved to the corresponding layer directory; saving to any other location is not permitted.

---

## 1. Strategy Layer

### 1.1 Product Strategy
- Template: `.cursor/myprdskill-en/skills/create-new-product-desing_guide/assets/templates/Product-Strategy-Design.md`
- Instructions: Read the template, fill it in based on the user's requirements, and produce the Product Strategy document. This document is the foundation for all subsequent design decisions; any design MUST strictly follow it.
- Save to: `PRD/1-Strategy/Product-Strategy-Design.md`

### 1.2 User Personas
- Template: `.cursor/myprdskill-en/skills/create-new-product-desing_guide/assets/templates/User-Persona.md`
- Instructions: Based on the product strategy, generate one User Persona document for each user type.
- Save to: `PRD/1-Strategy/{user-type-id}-Persona.md` (one file per user type)

### 1.3 User Story Maps
- Index template: `.cursor/myprdskill-en/skills/create-new-product-desing_guide/assets/templates/User-Story-Map/INDEX.md`
- Single map template: `.cursor/myprdskill-en/skills/create-new-product-desing_guide/assets/templates/User-Story-Map/_TEMPLATE.md`
- Instructions: First read INDEX.md to understand the directory structure, then generate a separate story map file for each user type.
- Save to: `PRD/1-Strategy/User-Story-Map/{user-type-id}-Story-Map.md` (one file per user type)

---

## 2. Scope Layer

### 2.1 Iteration Roadmap
- Template: `.cursor/myprdskill-en/skills/create-new-product-desing_guide/assets/templates/Iteration-Roadmap.md`
- Instructions: Based on the three Strategy Layer documents, plan the product version roadmap, specifying the scenario each version addresses and the features it includes.
- Save to: `PRD/2-Scope/Iteration-Roadmap.md`

### 2.2 Business Flow
- Template: `.cursor/myprdskill-en/skills/create-new-product-desing_guide/assets/templates/Business-Flow.md`
- Instructions: Based on the Strategy Layer documents and Iteration Roadmap, draw a user-perspective operation flow diagram (Mermaid) for each key scenario. No technical implementation details.
- Save to: `PRD/2-Scope/Business-Flow.md`

### 2.3 Feature List
- Template: `.cursor/myprdskill-en/skills/create-new-product-desing_guide/assets/templates/Feature-List.md`
- Instructions: Based on the Strategy Layer documents, Iteration Roadmap, and Business Flow, generate a hierarchical feature list grouped by version (max 5 levels; the deepest level must describe precise interaction logic).
- Save to: `PRD/2-Scope/Feature-List.md`

---

## 3. Structure Layer

### 3.1 Entity Requirements
- Template: `.cursor/myprdskill-en/skills/create-new-product-desing_guide/assets/templates/Entity-Requirements.md`
- Instructions: Based on the Feature List, generate a separate requirements document for each independent entity. Subordinate entities are documented inside their parent entity's file and do not get their own file.
- Save to: `PRD/3-Structure/{EntityName}-Requirements.md` (one file per independent entity)

---

## 4. Presentation Layer

### 4.1 UI Structure
- **No UI needed**: Apply the minimum viable principle to determine whether a UI is necessary. If not, explain the reasoning and recommendation; skip steps 4.1 and 4.2.
- **UI needed**:
  - Confirm interface type: CLI / Web_PC / Web_Mobile / Other
  - Template: `.cursor/myprdskill-en/skills/create-new-product-desing_guide/assets/templates/UI-Structure.md`
  - Instructions: Based on the Business Flow and interface type, generate a navigation flow diagram (Mermaid) plus per-page content descriptions.
  - Save to: `PRD/4-Presentation/UI-Structure.md`

### 4.2 UI Prototype
- **No UI needed**: Skip this step.
- **UI needed**: Based on the UI Structure document, generate an ASCII or Markdown wireframe for each page.
- Save to: `PRD/4-Presentation/UI-Prototype/{PageName}.md` (one file per page)
