product-planning

Files (13)

• SKILL.md
• SKILL_ja.md
• evaluation-criteria.md · references/
• persona-template.md · references/
• policy-output-structure.md · references/
• policy-web-search.md · references/
• 01_environment.md · references/prompts/marketing/
• 02_strategy.md · references/prompts/marketing/
• 03_concept.md · references/prompts/marketing/
• 04_plan.md · references/prompts/marketing/
• 01_pr_faq.md · references/prompts/working-backwards/
• 02_review.md · references/prompts/working-backwards/
• 03_final_review.md · references/prompts/working-backwards/

SKILL.md (first lines)

# Product Planning Workshop Skill

## Overview

A workshop skill that advances product planning through interactive dialogue with an AI coding agent. It provides three sub-modes:

| Sub-mode | How to invoke | Purpose |
|---|---|---|
| **A. Production Workshop** | Natural language (e.g., "I want to do product planning", "start a new product plan") | Advance actual product planning with dialogue between participants and the agent |
| **B. Dry Run Execution** | Natural language (e.g., "run a dry run", "try the workshop with a scenario") | AI autonomously runs the workshop as a persona from an existing scenario. Used for quality validation and learning |
| **C. Scenario Creation** | Natural language (e.g., "create a scenario", "make a persona for dry run") | Interactively generate `persona.md` used by dry runs |

> Note: the only explicit slash-command entry point is `/product-planning`. Modes are dispatched from the post-activation dialogue via natural language.

Within each sub-mode, choose one of two workshop "approach modes":

| Approach Mode | Steps | Characteristics |
|---|---|---|
| 🔍 Marketing-first | 4 steps | Build strategy from analysis of existing markets. Data-driven |
| 📰 Working Backwards | 3 steps | Reverse-engineer from customer experience to invent what is not yet in the market. Amazon style |

The output structure, file naming, and project-slug determination rules are defined in `references/policy-output-structure.md`. Always consult it.

The web-search date policy is defined in `references/policy-web-search.md`. Always consult it.

---

## Path semantics (must read)

Paths mentioned in this skill fall into **two categories** with different base points. Mixing them up leads to reading non-existent directories and failing, so always be aware of which category a path belongs to.

| Prefix | Base point | Purpose |
|---|---|---|
| `references/...` | **The skill's own directory** (same folder as `SKILL.md`, e.g., `/path/to/skills/product-planning/`) | Load prompts, policies, and templates bundled with the skill |
| `dry-run-scenarios/...` | **The user's working directory** (the current working directory / CWD when `kiro-cli` is invoked) | Scenario placement for Dry Run (input/output of Mode B and Mode C) |
| `product-planning/...` | **The user's working directory** (same as above) | Output of workshop deliverables (Mode A and Mode B) |

⚠ Do not look for `dry-run-scenarios/` or `product-planning/` under the skill directory. They always refer to directories directly under the user's working directory.

If the corresponding directory does not yet exist in the user's working directory, follow each mode's initialization flow (project-slug determination in Mode A, scenario detection in Mode B, scenario placement in Mode C) and create it as needed. The absence of the directory itself is not an error.

---

## Mode Detection (dispatch at invocation)

Upon skill activation, determine the mode in this order:

1. Input expresses scenario-creation intent ("create a scenario", "make a persona", "シナリオを作りたい", "ペルソナを作成したい") → **Mode C**
2. Input expresses dry-run-execution intent ("run a dry run", "try with a scenario", "Dry Run を実行したい") → **Mode B**
3. Otherwise, workshop intent such as "product planning", "new product", "商品企画", "Working Backwards" → **Mode A**
4. When ambiguous, ask the user which mode to use

---

## Mode A: Production Workshop

### Behavior at activation

1. Help the participant choose an approach mode:
   - Marketing-first: "build strategy from analysis of existing markets"
   - Working Backwards: "reverse-engineer from customer experience to invent what is not yet in the market"
2. Once the mode is chosen, **before loading the Step 1 prompt**, finalize the project-slug (see below)
3. After the project-slug is finalized, load the Step 1 prompt of the chosen mode from `references/prompts/{mode}/` and start execution
4. At the end of each step, automatically load the next step's prompt and continue

### project-slug determination flow (required)

Immediately after mode selection, execute the following:

1. List existing subdirectories under `product-planning/{mode}/` in the user's working directory
2. If existing plans are found, confirm with the participant:
   ```
   Found existing plans:
   - smart-insurance (last updated: 2026-02-01)
   - kids-fintech-app (last updated: 2026-04-15)

   Continue an existing plan, or start a new one?
   ```
   - Continue: use that slug and resume
   - New: proceed to next step
3. For a new plan:
   - Ask the participant: "Please give a short English name for this plan's theme (e.g., `smart-insurance`)"
   - If they answer in Japanese, propose 2-3 slug candidates and let them choose
   - Normalize to kebab-case (lowercase, spaces → hyphens, remove special chars)
4. Once finalized, create `product-planning/{mode}/{project-slug}/` and clearly state the output location to the participant. Use a visual message such as:

   ```
   📁 Deliverables for this workshop will be written to:
      product-planning/{mode}/{project-slug}/
      ├── 01_xxx.md  … Step 1
      ├── 02_xxx.md  … Step 2
      └── ...
   ```

   This lets the participant immediately see which files to open in the Markdown preview while the workshop runs.

See `references/policy-output-structure.md` for details.

### Step progression

At each step, load the designated prompt and execute. Deliverables go under `product-planning/{mode}/{project-slug}/`, with numeric filename prefixes so the order is visible.

#### Marketing-first mode (4 steps)

| Step | Prompt | Deliverable (under `product-planning/marketing/{project-slug}/`) |
|---|---|---|
| 1 | `references/prompts/marketing/01_environment.md` | `01_environment.md` (+ optional splits such as `01_environment_pest.md`) |
| 2 | `references/prompts/marketing/02_strategy.md` | `02_strategy.md` |
| 3 | `references/prompts/marketing/03_concept.md` | `03_concept.md` |
| 4 | `references/prompts/marketing/04_plan.md` | `04_plan.md` |

#### Working Backwards mode (3 steps)

| Step | Prompt | Deliverable (under `product-planning/working-backwards/{project-slug}/`) |
|---|---|---|
| 1 | `references/prompts/working-backwards/01_pr_faq.md` | `01_pr_faq.md` (first draft) |
| 2 | `references/prompts/working-backwards/02_review.md` | `02_pr_faq.md` (revised — a new file derived from `01_pr_faq.md` with Step 2 deep-dive reflected) + `02_review_*.md` supporting files |
| 3 | `references/prompts/working-backwards/03_final_review.md` | `03_pr_faq.md` (final — a new file derived from `02_pr_faq.md` with the final review reflected) + `03_executive_summary.md` |

From aws-samples/sample-fsi-reference-architecture-jp, MIT-0.

More from aws-samples/sample-fsi-reference-architecture-jp