abstract-to-concreate-design

Add context to the design project workspace. Paste MoMs, emails, Slack threads, research docs, or stakeholder notes. Agent reflects back understanding and surfaces gaps.

Fire all specialist agents. Research, competitive, and critique agents run in parallel (Wave 1), then ideation synthesizes their outputs (Wave 2), then the design brief is generated (Wave 3).

Validate problem understanding, stakeholder alignment, context freshness, and gap analysis before proceeding to ideation. Run after design:feed (pre-agent) and after Wave 1 (post-research).

Internal orchestrator — manages wave scheduling and agent dispatch for design:run. Not user-invokable. Called by design:run skill.

Generate or regenerate DESIGN-BRIEF.md from existing agent outputs. Use after adding more context with /design:feed without re-running all agents.

Specialist agent — maps the competitive landscape and surfaces patterns and gaps. Outputs COMPETITIVE.md. Dispatched by design:run orchestrator.

Specialist agent — audits the current UX using the production URL or screenshot. Outputs CRITIQUE.md with severity-rated findings. Dispatched by design:run orchestrator.

Specialist agent — synthesizes all Wave 1 outputs into a reframed problem and design tensions. No directions. No solutions. Outputs IDEATION.md. Dispatched by design:run orchestrator after Wave 1 completes.

Specialist agent — synthesizes pasted context from BRIEF.md into a structured UX problem statement. Outputs RESEARCH.md. Dispatched by design:run orchestrator.

Create a new design project workspace. Initializes the .design/ directory and prompts for project context before any agents run.

Show current workspace state — what context has been fed, which agents have run, what gaps remain.