Leadership
Designer Decision Stack
Prepare a designer decision queue. Uses time window, project key, person, launch.
Configure this skill
The page and the file follow your answers.
CRM
Email
Chat
Documents
Calendar
Project tools
6 of 6 systems connected
KeepDirectMissing
Your assistantSKILL.md
Download ↓
When to use it
Prepare a designer decision queue.
What it covers
Inputs
Decision question, owner/authority, deadline, criteria.
Result
Decision question, options/tradeoffs, recommendation or unresolved choice and required next evidence.
What it uses
CalendarEmailDocumentsSlackProject toolsCRMKeep memory
For developers
Retrieval instructions
Resolve people, accounts and projects by stable identifiers. Use only the sources this task needs. Cite the source and date for each finding. Keep source systems unchanged.
Data sources
Google Workspace, Slack, Linear, Attio, Keep memory.
Procedure
- Resolve inputs for Designer Decision Stack: time_window, project_key, person, launch. Default time window: this week company operating horizon (override if caller provides time_window). Ask only for missing critical.
- keep_memory_read for open tasks, decisions, and handoffs relevant to Designer Decision Stack (filter out unrelated day-plan noise).
- Designer lens: Prefer sources , design docs, critique threads, Linear design tickets, Slack #design. Role ranking bias: launch-critical → review blockers → research asks → polish.