---
title: Pipeline Dependency Graph
description: Phase execution order and profiles via skill-dependencies.yaml
seo:
  image: /ogp.png
---
The `product` plugin has a single configuration file: `skill-dependencies.yaml`. This is the single source of truth for the plugin.
It defines the dependencies for each phase, whether each phase is implemented (`implemented: true`), and where its output goes.
`/product:start` reads this file to determine the execution order.
The profile (`mvp`, `core-only`, `ux-to-spec`, or `full`) determines which phases are included in the run.

Specify a profile with `--profile`. If omitted, `full` is used.

```
/product:start --profile=mvp
```

| Profile | Phases | Use case |
|---|---|---|
| `mvp` | 3 | Get a Go/No-Go decision as quickly as possible |
| `core-only` | 6 | Establish the business viability skeleton |
| `ux-to-spec` | 10 | Vision/Scope already defined; drive through to spec |
| `full` | 24 | End-to-end from Vision through architecture (default) |

```yaml
profiles:
  mvp:        [define-vision, define-scope, validate-assumptions]
  core-only:  [define-vision, define-success-metrics, research-landscape, design-revenue, define-scope, validate-assumptions]
  ux-to-spec: [generate-persona, map-journey, design-positioning, create-domain-story, design-system, generate-ui-mock, define-features, example-map, define-data-model, generate-frontend]
  full:       [define-vision, name-product, define-success-metrics, research-landscape, design-revenue, define-scope,
               validate-assumptions, generate-persona, map-journey, design-positioning, create-domain-story,
               design-system, generate-ui-mock, define-features, example-map, define-data-model, generate-frontend,
               map-domains, design-api, design-sla, define-nfr, design-architecture, review, report]
```

## Overall flow

The `full` profile consists of five phases separated by validation gates.
The high-level structure is shown below. Yellow nodes are validation gates.

```mermaid
flowchart LR
  P1["Phase 1<br/>事業の方向性"] --> G{{"検証ゲート<br/>Go/No-Go"}}
  G --> P2["Phase 2<br/>UX/ドメイン"]
  P2 --> P3["Phase 3<br/>仕様"]
  P3 --> P4["Phase 4<br/>ドメイン/API"]
  P4 --> P5["Phase 5<br/>品質要件"]
  P5 --> F["design-architecture<br/>統合"]
  F --> R["review → report"]

  classDef gate fill:#fef3c7,stroke:#f59e0b
  class G gate
```

## Phase details

The execution order within each phase is shown below. Dashed lines indicate optional phases that run conditionally.

**Phase 1**

Defines the business direction and scope. After `define-scope` completes, the pipeline enters the validation gate.

```mermaid
flowchart TD
  A1["define-vision<br/>Visionを定義"] --> A2["define-success-metrics<br/>North Star Metricを定義"]
  A2 --> A3["research-landscape<br/>市場規模(TAM/SAM/SOM)を調査"]
  A3 --> A4["design-revenue<br/>収益モデルを設計"]
  A4 --> A5["define-scope<br/>やる範囲を決める"]
  A5 --> G{{"validate-assumptions<br/>Go/No-Go判定"}}
  A1 -.->|任意| N1["name-product<br/>プロダクト名を生成"]

  classDef gate fill:#fef3c7,stroke:#f59e0b
  classDef optional fill:#f3f4f6,stroke:#9ca3af,stroke-dasharray: 3 3
  class G gate
  class N1 optional
```

**Phase 2**

Designs who uses the product and how. `design-system` belongs to this phase but can be run independently.

```mermaid
flowchart TD
  B1["generate-persona<br/>ペルソナを作る"] --> B2["map-journey<br/>ジャーニーマップを作る"]
  B2 --> B3["design-positioning<br/>ポジショニングを設計"]
  B3 --> B4["create-domain-story<br/>業務の流れを図にする"]
  B4 -.->|独立実行可| N2["design-system<br/>デザインシステムを構築"]

  classDef optional fill:#f3f4f6,stroke:#9ca3af,stroke-dasharray: 3 3
  class N2 optional
```

**Phase 3**

Produces specs at an implementable level of detail. `generate-frontend` is optional and generates a React + Storybook implementation.

```mermaid
flowchart TD
  C1["generate-ui-mock<br/>UIモックを作る"] --> C2["define-features<br/>機能を定義"]
  C2 --> C2b["example-map<br/>業務ルールを具体例で洗い出す"]
  C2b --> C3["define-data-model<br/>データモデルを定義"]
  C3 -.->|任意| N3["generate-frontend<br/>フロントエンドを生成"]

  classDef optional fill:#f3f4f6,stroke:#9ca3af,stroke-dasharray: 3 3
  class N3 optional
```

**Phase 4 & 5**

Domain decomposition and API design (Phase 4), followed by quality requirements definition (Phase 5). After these complete, the pipeline moves to integration and review.

```mermaid
flowchart TD
  D1["map-domains<br/>ドメインを分割"] --> D2["design-api<br/>APIを設計"]
  D2 --> E1["design-sla<br/>SLAを設計"]
  E1 --> E2["define-nfr<br/>NFRを定義"]
  E2 --> F["design-architecture<br/>アーキテクチャを設計"]
  F --> R1["review<br/>4視点でレビュー"] --> R2["report<br/>統合レポートを作成"]
```

## Profile differences

<Accordion>
  <AccordionItem title="mvp — Get a Go/No-Go decision as fast as possible">
    The smallest profile. It defines <Tooltip tip="このプロダクトで何を実現したいのかを言葉にしたもの。パイプラインの出発点です。" headline="Vision" cta="用語集で見る" href="/glossary">Vision</Tooltip> and <Tooltip tip="今回やる範囲と、やらない範囲。MoSCoWやRICEスコアで決めます。" headline="Scope" cta="用語集で見る" href="/glossary">Scope</Tooltip>, then immediately runs `validate-assumptions` to confirm a plan for validating the underlying assumptions.
  </AccordionItem>
  <AccordionItem title="core-only — Establish the business viability skeleton">
    A profile for evaluating whether the business is viable. It covers the <Tooltip tip="その事業が最も重視する、成功を測る1つの指標。" headline="North Star Metric" cta="用語集で見る" href="/glossary">North Star Metric</Tooltip>, <Tooltip tip="狙える市場規模を3段階で表す指標。市場全体の大きさ(TAM)、自社が狙える範囲(SAM)、実際に取れそうなシェア(SOM)。" headline="TAM / SAM / SOM" cta="用語集で見る" href="/glossary">TAM/SAM/SOM</Tooltip>, and the revenue model.
  </AccordionItem>
  <AccordionItem title="ux-to-spec — Drive straight from UX to implementable spec">
    A profile that assumes Vision and Scope are already defined. It runs straight through from persona generation to UI mocks, feature definition, and data modeling.
  </AccordionItem>
  <AccordionItem title="full — All 24 phases from Vision through architecture">
    Runs all 24 phases. Covers everything from defining the Vision through review and producing the final integrated report. This is the path taken in the [hands-on example: EASE](/tutorial).
  </AccordionItem>
</Accordion>