# Product Rd

> Execute product R&D phases for a Notion task ticket by reading the PM workflow framework and the task content from Notion, then carrying out the specified phases. Use when the user says "/product-rd", "product rd", "product R&D", "execute phase", or provides a Notion task link with phase numbers.

- Skill: `rayliu66/product-rd` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add rayliu66/product-rd`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rayliu66/product-rd/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: Rayliu66 (https://skillmd.com/u/rayliu66)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/rayliu66/product-rd

---


# Product R&D — Execute Phases

When this skill is invoked, **read the framework and task from Notion, then execute the requested phase(s)**. Do NOT just output a prompt — actually do the work.

## Required Inputs

| Input | Description | Example |
|-------|-------------|---------|
| **Task Notion ticket link** | Full Notion URL of the task | `https://www.notion.so/woolfuniversity/...` |
| **P** | Phase number(s) to execute | `3` or `2,3,4` |

If either input is missing, ask the user:
- "Please provide the Task Notion ticket link."
- "Please provide the P value (Execute Phase number(s)), e.g. `3` or `2,3,4`."

## Execution Steps

### Step 1: Fetch the PM Workflow Framework

Read the framework document from Notion:

```
https://www.notion.so/PM-WF-2-3-32e8d41a5cff8082a897f6c3fa5b2757?source=copy_link
```

Use the Notion MCP tool (`notion-fetch`) to retrieve its full content. This framework defines what each phase involves, its checkpoints, deliverables, and acceptance criteria.

### Step 2: Fetch the Task Notion Ticket

Read the task ticket from Notion using the user-provided link. Extract:
- Task description and requirements
- Any existing deliverables or context from prior phases
- Acceptance criteria
- Related links or references

If the user also provides a **structure document** link, fetch that too — it provides architectural context for the task.

### Step 3: Execute the Requested Phase(s)

Follow the framework's instructions for each requested phase number. Carry out the work described: analysis, design, implementation, documentation, or whatever the phase requires.

**Work through each phase sequentially**, producing the deliverables the framework specifies for that phase.

### Step 4: Checkpoints and Auto-Approve

After completing each phase, present its checkpoint to the user for review.

**Auto-approve logic for multi-phase runs:**

When P contains **more than one phase**, auto-approve all checkpoints **except the last one** (proceed without pausing for user confirmation).

| P value | Execute | Auto-approve | Pause at |
|---------|---------|--------------|----------|
| `3` | Phase 3 | — | Checkpoint 3 |
| `2,3` | Phase 2, 3 | Checkpoint 2 | Checkpoint 3 |
| `2,3,4` | Phase 2, 3, 4 | Checkpoint 2, 3 | Checkpoint 4 |
| `2,3,4,5` | Phase 2, 3, 4, 5 | Checkpoint 2, 3, 4 | Checkpoint 5 |

Rule: all phase numbers except the last → auto-approve those checkpoints and continue. **Always pause at the final checkpoint** for user review.

When P is a **single phase**, pause at that phase's checkpoint for user review.

### Step 5: Deliver Results

After all phases are complete (and final checkpoint approved), summarize what was produced and update the Notion task ticket if appropriate.

## Formatting Rules

1. List phases with commas and "and" before the last one (e.g. "2, 3 and 4")
2. List auto-approve checkpoints with commas (e.g. "CHECKPOINT 2, 3")
3. Always show which checkpoint you are at and whether it is auto-approved or awaiting user review