Three Workflows

The toolkit supports three distinct workflows, each designed for a different type of work.

At a glance

graph TB
    subgraph dev["Development Workflow"]
        direction LR
        D0["/0-start"] --> D1["/1-bootstrap"] --> D2["/2-plan"] --> D3["/3-build"] --> D4["/4-review"] --> D5["/5-deploy"] --> D6["/6-operate"]
    end

    subgraph pd["Product Design Workflow"]
        direction LR
        P0["/pd-0-start"] --> P1["/pd-1-research"] --> P2["/pd-2-prd"] --> P3["/pd-3-prototype"] --> P4["/pd-4-validate"] --> P5["/pd-5-specchen"] --> P6["/pd-6-handoff"]
    end

    subgraph kw["Knowledge Work Workflow"]
        direction LR
        K0["/kw-0-start"] --> K1["/kw-1-plan"] --> K2["/kw-2-execute"] --> K3["/kw-3-review"] --> K4["/kw-4-publish"]
    end

Which workflow should I use?

If you're...	Use	Start with
Building software (APIs, apps, services)	Development	/0-start
Designing a product (research, PRD, prototype)	Product Design	/pd-0-start
Creating non-code deliverables (docs, research, processes)	Knowledge Work	/kw-0-start

Not sure?

Start with /0-start, /pd-0-start, or /kw-0-start. Each shows the full workflow for its type and validates that your project is ready.

Development Workflow

7 phases for building software from idea to production.

Phase	Command	What happens
0. Start	/0-start	See the workflow, validate readiness
1. Bootstrap	/1-bootstrap	Scaffold project structure
2. Plan	/2-plan	Architecture and spec via conceptual orchestrator
3. Build	/3-build	Implementation with knowledge capture
4. Review	/4-review	6 parallel code reviewers
5. Deploy	/5-deploy	Pre-deploy verification
6. Operate	/6-operate	Bug investigation and incident response

See Development Workflow for the full guide.

Product Design Workflow

7 phases + iterative loop for designing products before code.

Phase	Command	What happens
0. Start	/pd-0-start	See the workflow, validate readiness
1. Research	/pd-1-research	User interviews, personas, analysis
2. PRD	/pd-2-prd	Product Requirements Document
3. Prototype	/pd-3-prototype	Deployable HTML/React prototype
4. Validate	/pd-4-validate	Usability testing with real users
5. SPECchen	/pd-5-specchen	Break PRD into implementation briefs
6. Handoff	/pd-6-handoff	Development handoff package

The product design workflow also includes an iterative design loop (/pd-inbox-scan → /pd-analyze-changes → /pd-route-decision) that lets you respond to new feedback without restarting the whole workflow.

See Product Design Workflow for the full guide.

Knowledge Work Workflow

5 phases for non-code deliverables like documentation, research, and processes.

Phase	Command	What happens
0. Start	/kw-0-start	See the workflow, validate readiness
1. Plan	/kw-1-plan	Define approach, structure, and risks
2. Execute	/kw-2-execute	Do the work with learning capture
3. Review	/kw-3-review	Quality review without code assumptions
4. Publish	/kw-4-publish	Finalize and deliver

See Knowledge Work Workflow for the full guide.

How workflows connect

Workflows aren't isolated. A typical product might flow through all three:

1. Product Design — research users, write the PRD, prototype and validate
2. Development — build the validated design into production code
3. Knowledge Work — create user guides, training materials, process docs

The handoff from Product Design (Phase 6) naturally feeds into Development (Phase 1).