design-brief

Draft an eight-field design brief from codebase signals and user context.

3|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/metedata/design-crit --skill design-brief-metedata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-brief
Source: https://github.com/metedata/design-crit/tree/main/skills/design-brief
Command: npx skills add https://github.com/metedata/design-crit --skill design-brief-metedata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Design Brief helps start a design project by capturing knowns, exposing gaps, and guiding the team before heavy visual work. It surfaces context from the codebase and user input, frames questions, and yields a draft brief that can be reviewed and refined in the terminal.

Core Features & Use Cases

  • Harvest context from the project codebase and user conversations to inform the brief.
  • Draft the eight-field brief (project name/description, target users and context, core interaction loop, differentiator, platform and constraints, scope, existing design language, and accessibility requirements).
  • Surface inline notes for any fields inferred from available signals and prompt for confirmation.
  • Generate a read-only overview of the confirmed brief as a reference page after the brief is finalized.
  • Operate entirely in the terminal without interactive HTML during the brief stage; the briefing step prepares the ground for later design critique.

Quick Start

Draft a Design Brief by summarizing what you know about the project and explicitly calling out gaps.

Frequently Asked Questions about design-brief

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

FAQPage Schema
How do I write a structured design brief from existing codebase signals?

A design brief captures known project context and exposes gaps before visual work begins. It harvests signals from the codebase and user input to frame questions and yield a draft suitable for design critique.

How do I document design requirements and identify gaps before starting visual work?

Drafting a design brief involves summarizing known project context and explicitly calling out gaps. It produces a structured brief with eight fields, including platform constraints and accessibility requirements, stored as a markdown file.

What is the best way to prepare a project for a design critique?

A confirmed design brief is stored as a .design-crit/brief.md file. It updates the pipeline state and generates a read-only overview reference page to support subsequent facet planning and design critique.

Does the design briefing process require interactive HTML or a specific platform?

The design briefing process operates entirely in the terminal without interactive HTML during the brief stage. It relies on analyzing codebase signals and user context to produce the defined brief fields.

Can I infer accessibility requirements and design language from an existing project?

Yes, accessibility requirements and existing design language can be inferred from available codebase signals. The brief surfaces these as inline notes and prompts for stakeholder confirmation before finalizing the document.