---
name: iterative-product-design-guide
description: Iterative product design work standard. Use when the user needs to perform product design work for an existing product iteration — collecting requirements, triaging against the roadmap, and delivering updated PRD documents for the target version.
---

# Iterative Product Design Guide

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

## Working Principles

- Pause after each phase and wait for user confirmation before continuing
- All design decisions MUST align with `PRD/2-Scope/Iteration-Roadmap.md`; any deviation is an error
- Follow the minimum viable principle: update only what is necessary for this iteration
- The iteration node is defined by the version in the Iteration Roadmap — do not invent new versions

---

## File Organization

### Persistent Collection Files (shared across all iterations)

Ensure the following files exist in the project. Create them from templates if they do not exist:

```
PRD/
├── Feedback/
│   └── User-Feedback.md         ← user feedback across all versions
└── Optimization/
    └── Optimization-Requirements.md  ← team & roadmap-inspired optimization ideas
```

- `User-Feedback.md` template: `.cursor/myprdskill-en/skills/iterative-Product-Design-Guide/assets/templates/User-Feedback.md`
- `Optimization-Requirements.md` template: `.cursor/myprdskill-en/skills/iterative-Product-Design-Guide/assets/templates/Optimization-Requirements.md`

### Iteration Version Folder (created per iteration)

Each iteration produces its own folder containing the triage document and all updated PRD files:

```
PRD/
└── iterations/
    └── v{VERSION}/
        ├── Iteration-Requirements.md   ← triage & confirmed scope for this version
        └── (updated PRD files — copies of changed files only)
```

All modified PRD deliverables for the iteration MUST be placed inside `PRD/iterations/v{VERSION}/`, mirroring the layer path. For example:
- An updated Feature List goes to `PRD/iterations/v{VERSION}/2-Scope/Feature-List.md`
- An updated Entity Requirement goes to `PRD/iterations/v{VERSION}/3-Structure/{EntityName}-Requirements.md`

Do **not** overwrite the original PRD files under `PRD/1-Strategy/` through `PRD/4-Presentation/` directly. The iteration folder is the source of truth for the dev team.

---

## Phase 0 — Read Current PRD Baseline

Before any triage work, read the following documents to understand the current product state:

1. `PRD/2-Scope/Iteration-Roadmap.md` — identify the **target version** for this iteration and its stated goal/scenario
2. `PRD/1-Strategy/Product-Strategy-Design.md` — confirm product positioning and constraints
3. `PRD/2-Scope/Feature-List.md` — understand what already exists
4. `PRD/Feedback/User-Feedback.md` — review all `Open` user feedback items
5. `PRD/Optimization/Optimization-Requirements.md` — review all `Open` optimization items

After reading, summarize:
- The target iteration version and its roadmap goal
- The count of Open user feedback items
- The count of Open optimization items

**Confirm with user before proceeding.**

---

## Phase 1 — Requirements Triage

### 1.1 Create the Iteration Requirements Document

Create the iteration version folder and initialize the triage document:

- Copy template: `.cursor/myprdskill-en/skills/iterative-Product-Design-Guide/assets/templates/Iteration-Requirements.md`
- Save to: `PRD/iterations/v{VERSION}/Iteration-Requirements.md`
- Fill in the version info section and the candidate requirements table (Step 1) from all `Open` items in `User-Feedback.md` and `Optimization-Requirements.md`

### 1.2 Triage Each Candidate

For each candidate requirement, assess and fill in the triage table (Step 2):

**Roadmap Alignment**: Does this requirement serve the scenario/goal of the target version as defined in `Iteration-Roadmap.md`?
- `Yes` — directly supports the version's stated scenario or features
- `No` — outside the scope of this version's roadmap goal

**Priority**: Based on the nature of the requirement and user/team judgment:

| Priority | Meaning |
|----------|---------|
| `High` | Must be implemented as soon as possible — directly blocks user value or fixes a critical issue |
| `Medium` | Valuable but not blocking — should be included if High items are all in scope |
| `Low` | Nice to have — defer unless there is remaining capacity and explicit user confirmation |

**Decision Rules**:
- Aligned + High → `Include`
- Aligned + Medium → `Include` after all High items are confirmed in scope
- Aligned + Low → `Defer`; present to user separately and wait for explicit confirmation before moving to `Include`
- Not Aligned → `Exclude` from this iteration; do **not** remove from source file

### 1.3 Present Low-Priority Items to User

If any Aligned + Low items exist, list them explicitly and ask the user whether to include any of them in this iteration before finalizing the scope.

### 1.4 Finalize Iteration Scope

Complete Step 3 (Confirmed Iteration Scope) in `Iteration-Requirements.md`:
- List only `Include` items
- For each item, identify which PRD layers it affects: `Strategy`, `Scope`, `Structure`, `Presentation`
- Summarize the affected files per layer

Update the source collection files:
- Mark included items as `Triaged(v{VERSION})` in `User-Feedback.md` and `Optimization-Requirements.md`
- Mark excluded items as `Closed` with a brief reason

**Confirm iteration scope with user (Step 4 of Iteration-Requirements.md) before proceeding.**

---

## Phase 2 — Requirements Analysis & PRD Updates

For each confirmed requirement in the iteration scope, perform design work on the affected PRD layers. Process layers in order: Strategy → Scope → Structure → Presentation.

### Layer Update Rules

- **Only update files that are actually affected** by the confirmed requirements
- Each updated file is placed in `PRD/iterations/v{VERSION}/{layer-folder}/{filename}`
- Base each update on the current version of the file in `PRD/{layer-folder}/{filename}`
- Changes MUST be limited to what the confirmed requirements call for — no scope creep

### 2.1 Strategy Layer (if affected)

Affected files may include:
- `Product-Strategy-Design.md` — only if product positioning, target users, or core value changes
- `{user-type-id}-Persona.md` — only if a user type's profile, goals, or pain points change
- `User-Story-Map/{user-type-id}-Story-Map.md` — only if user journeys change

For each affected file:
- Read the current version from `PRD/1-Strategy/`
- Apply only the changes required by the confirmed requirements
- Save to `PRD/iterations/v{VERSION}/1-Strategy/{filename}`

**Pause and confirm with user before proceeding to Scope Layer.**

### 2.2 Scope Layer (if affected)

Affected files may include:
- `Iteration-Roadmap.md` — update only if the version description itself changes
- `Business-Flow.md` — update if any user-facing operation flow changes
- `Feature-List.md` — update to add, modify, or remove features per confirmed requirements

For each affected file:
- Read the current version from `PRD/2-Scope/`
- Apply only the changes required by the confirmed requirements
- Save to `PRD/iterations/v{VERSION}/2-Scope/{filename}`

**Pause and confirm with user before proceeding to Structure Layer.**

### 2.3 Structure Layer (if affected)

Affected files may include:
- `{EntityName}-Requirements.md` — update for any entity whose attributes, rules, or behaviors change; create a new file if a new entity is introduced

For each affected file:
- Read the current version from `PRD/3-Structure/`
- Apply only the changes required by the confirmed requirements
- Save to `PRD/iterations/v{VERSION}/3-Structure/{EntityName}-Requirements.md`

**Pause and confirm with user before proceeding to Presentation Layer.**

### 2.4 Presentation Layer (if affected)

Affected files may include:
- `UI-Structure.md` — update if navigation flow or page inventory changes
- `UI-Prototype/{PageName}.md` — update for each page whose layout or content changes; create a new file for new pages

For each affected file:
- Read the current version from `PRD/4-Presentation/`
- Apply only the changes required by the confirmed requirements
- Save to `PRD/iterations/v{VERSION}/4-Presentation/{filename or subfolder/filename}`

**Pause and confirm with user before proceeding.**

---

## Phase 3 — Delivery Notification

After all affected PRD layers are updated and confirmed by the user:

1. Verify that the `PRD/iterations/v{VERSION}/` folder contains:
   - `Iteration-Requirements.md` (with Step 4 confirmed)
   - All updated PRD files organized by layer subfolder
2. Notify the development team with the following message:

---

> **[Product Design → Dev Team]**
>
> Iteration **v{VERSION}** product design is complete. All updated PRD documents are ready for review.
>
> **Iteration folder**: `PRD/iterations/v{VERSION}/`
>
> **What's in this iteration**:
> (list each confirmed requirement with its Req ID and summary)
>
> **Affected PRD files**:
> (list each updated file with its path inside the iteration folder)
>
> Please read the iteration folder contents and proceed with iterative development using the `@dev_leader` agent and the `iterative-dev-guide` skill.

---

**The iterative product design for v{VERSION} is complete.**
