Abstract To Concreate Design

Abstract to Concrete Design

An agentic CLI workflow that moves designers from scattered context to evidence-based design brief — before they open Figma.

---

The Problem: Scattered Context

Designers face a common challenge:

• MoMs in Slack threads
• Research in Notion
• Stakeholder feedback in email
• Competitive intel in random docs
• Design critiques in head

Context lives everywhere. The designer holds it all in their head — or doesn't. Important insights get lost. Decisions get made without full picture.

**This system brings context together, validates understanding, and surfaces gaps — before design begins.**

---

How It Works

/design:new         → Create project workspace
       ↓
/design:feed        → Paste MoMs, emails, docs, Slack threads
       ↓
/design:validate    → Verify understanding, detect conflicts
       ↓
/design:run         → Run agents (Research → Competitive → Critique)
       ↓
/design:validate    → Validate research synthesis
       ↓
/design:brief       → Get your evidence-based brief
       ↓
Open Figma

---

The Scattered Context Solution

Before	After
MoMs in Slack	All context in .design/BRIEF.md
Research in Notion	Synthesized in RESEARCH.md
Competitive intel scattered	Mapped in COMPETITIVE.md
Feedback in emails	Traced to source in BRIEF.md
"What do we know?"	Check GAPS.md or run /design:status

---

Key Features

1. Context Centralization

Paste anything — MoMs, emails, research docs, Slack threads. The system accumulates all context in one place, traceable to source.

2. Validation Gates

Before agents run, validate your understanding:

• Stakeholder mapping: Who said what?
• Conflict detection: Do stakeholders contradict each other?
• Context freshness: How old is this information?

3. Gap Detection

The system surfaces what's missing:

• No user research data?
• No engineering constraints?
• Missing competiti