Workflows

The toolkit provides two primary workflows, aligned with the Two-Workflow Model defined in the constitution.

Starting a New Project

Run /0-init to create a new project. It asks one question — Product Development or Knowledge Work? — then creates the complete structure.

/0-init                          # Interactive — asks which workflow
/0-init product my-app           # Product Development project
/0-init knowledge market-research  # Knowledge Work project

Choosing the right workflow

graph TD
    INIT["/0-init"] -->|Product Development| PD[Product Design + Development]
    INIT -->|Knowledge Work| KW[Knowledge Work Workflow]
    PD -->|design phases| DESIGN["/vt-c-pd-1-research → /vt-c-pd-6-handoff"]
    DESIGN -->|handoff| DEV["/vt-c-activate → /vt-c-2-plan → /vt-c-3-build → /vt-c-4-review"]
    KW -->|work phases| KWFLOW["/vt-c-kw-1-plan → /vt-c-kw-4-publish"]

I want to...	Workflow	Start command
Start a new project	—	/0-init
Build an API or app	Development	/vt-c-0-start
Design a new product feature	Product Design	/vt-c-pd-0-start
Write documentation or research	Knowledge Work	/vt-c-kw-0-start

Workflow comparison

	Development	Product Design	Knowledge Work
Phases	7	6 + iterative loop	5
Output	Production code	Specs + handoff package	Published deliverables
Orchestrators	conceptual, implementation, deployment, bugfix, incident	product-design	knowledge-work
Code review	Yes (6 parallel reviewers)	No	No
Prototyping	No	Yes (HTML/React)	Optional
User research	No	Yes	Optional

Combining workflows

Real projects often use multiple workflows:

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

After Product Design handoff (/vt-c-pd-6-handoff), run /vt-c-specs-from-prd to generate implementation specs, then /vt-c-activate to start the Development workflow.