Pipeline Dependency Graph
Phase execution order and profiles via skill-dependencies.yaml
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) |
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.
Phase details
The execution order within each phase is shown below. Dashed lines indicate optional phases that run conditionally.
Defines the business direction and scope. After define-scope completes, the pipeline enters the validation gate.
Designs who uses the product and how. design-system belongs to this phase but can be run independently.
Produces specs at an implementable level of detail. generate-frontend is optional and generates a React + Storybook implementation.
Domain decomposition and API design (Phase 4), followed by quality requirements definition (Phase 5). After these complete, the pipeline moves to integration and review.
Profile differences
mvp — Get a Go/No-Go decision as fast as possible
core-only — Establish the business viability skeleton
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.
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.