# Write First Design

> Clarify uncertain product decisions in a short written brief before substantial design or implementation work.

- Skill: `kemiljk/write-first-design` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kemiljk/write-first-design`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kemiljk/write-first-design/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: kemiljk (https://skillmd.com/u/kemiljk)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/kemiljk/write-first-design

---


# Write-First Design

Use prose to resolve uncertain product decisions while changes are cheap. A clear user brief, existing decision document, or narrowly specified UI edit already provides direction; do not require another brief or approval step.

For substantial work with unclear intent, record the intended user outcome, proposed change, rationale, and useful non-goals. Keep this in the response or the project’s existing decision format unless a durable document helps the team.

A useful hypothesis is: “We believe [change] will produce [outcome] because [reason].” Adapt the wording to the decision; the outcome matters more than the template.

Explain meaningful design choices so a collaborator can evaluate them before investing in expensive implementation. Ask only about unresolved choices that would materially change the work. Otherwise state a reasonable assumption and continue within the authorized scope.

Keep the writer close to the builder. Update the rationale when implementation reveals a different tradeoff. Completion is the requested brief, or the implemented and verified change when implementation was requested.

## Source essays

- Write-first design
- Falling in love with the build
- Design for handshakes, not handovers