design-first

Present 2-3 design approaches and document decisions before implementation.

2|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/jlaws/dotfiles --skill design-first-jlaws
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-first
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/workflow/design-first
Command: npx skills add https://github.com/jlaws/dotfiles --skill design-first-jlaws

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures teams design and align on intent before coding, preventing rework and scope drift by requiring validated design approval prior to implementation.

Core Features & Use Cases

  • Phase-based process: explore context, ask clarifying questions, propose approaches, present design, document decisions, and transition to implementation.
  • Encourages explicit trade-offs, multiple approaches, and incremental validation to reduce risk and improve clarity.
  • Use Case: when starting a new feature, conduct a design-first brief and obtain sign-off before any coding starts.

Quick Start

Outline a feature design and obtain approval before starting implementation.

Frequently Asked Questions about design-first

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent scope drift and misalignment before starting feature implementation?

Gather requirements by exploring context and asking clarifying questions before proposing approaches. The design-first process explicitly encourages documenting trade-offs and incremental validation to improve clarity.

What is the best way to document architectural decisions during project planning?

Transition to implementation by obtaining formal design approval and sign-off first. The design-first workflow requires presenting a validated design and documenting decisions before any coding starts.

Does a design-first process require multiple approaches before coding begins?

A design-first approach prevents wasted work by requiring validated design approval prior to implementation, ensuring teams align on intent before coding. It is applied across exploration, requirements gathering, and design validation.

How does a design-first workflow handle feature requirements gathering?

No external dependencies are required. The design-first process operates independently across product development workflows, guiding exploration, requirements gathering, and design validation before coding.