# Router flow: Design / creative

## Entry signals
- "logo", "brand", "UI", "layout", "visual", "art"

## Steps
1) Interview for goals, audience, references, constraints.
2) Define deliverables and review cadence.
3) Generate requirements and design system structure.
4) Ask for approval or `--improve`.
5) Produce delivery checklist and accessibility checks.

## Required questions
- What is the message or brand?
- Who is the audience?
- What formats are needed?
- What constraints or references exist?
- What is the approval process?

## Required outputs
- `requirement.md`
- `functional-spec.md`
- `technical-spec.md`
- `architecture.md`
- `test-plan.md`

## Scripted Q/A tree

### Q1: Message and audience
Q: "What is the message and who is the audience?"  
A: capture audience and goal

### Q2: Deliverables
Q: "What formats are required (logo, web, print, social)?"  
A: capture deliverables

### Q3: References
Q: "Any style references or inspirations?"  
A: capture references

### Q4: Constraints
Q: "What constraints apply (timeline, budget, tools)?"  
A: capture constraints

### Q5: Approval cadence
Q: "Who approves and how often should we review?"  
A: capture review cadence

### Q6: Approval gate
Q: "Approve requirements and move to specs?"  
A: Yes -> generate specs  
A: No -> refine

## Gates
- Deliverables and approval process must be defined

## Agents
- Creative Lead, Design Systems, Critic