跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

write-first-design

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

kemiljk · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add kemiljk/skills --skill write-first-design

技能说明


name: write-first-design description: "Clarify uncertain product decisions in a short written brief before substantial design or implementation work." license: MIT

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