# Workflow Modes

Use these mode definitions when selecting how Da Vinci should start work.

## `greenfield-spec`

Use when:

- the project is new
- requirements are already clear enough to write specs

Entry artifacts:

- `design-brief.md`
- `proposal.md`
- `specs/<capability>/spec.md`
- `page-map.md`

Best for:

- 0-to-1 product work with a stable brief
- page sets that can be designed directly after requirement breakdown

## `greenfield-brainstorm`

Use when:

- the project is new
- requirements are spread across multiple rounds of rough ideas

Entry artifacts:

- `brainstorm.md`
- `design-brief.md`
- then `proposal.md`
- then `specs/<capability>/spec.md`
- then `page-map.md`

Best for:

- founder ideation
- product discovery sessions
- messy early-stage requests that need synthesis before design

## `redesign-from-code`

Use when:

- an existing project already has routes, pages, and UI
- the goal is a broad UI replacement or redesign

Entry artifacts:

- `project-inventory.md`
- `design-registry.md`
- `proposal.md`
- `specs/<capability>/spec.md`
- `page-map.md`

Best for:

- full visual refresh
- layout modernization
- design-system replacement

## `feature-change`

Use when:

- the project already exists
- the change affects only part of the system

Entry artifacts:

- `proposal.md`
- `specs/<capability>/spec.md`
- affected `design-registry.md`
- affected subset of `page-map.md`

Best for:

- new feature pages
- changing existing pages
- scoped UX or workflow changes