Design brief
Skill Infrasity-Labs/dev-gtm-claude-skills/.claude/skills/design-brief
Write a comprehensive design brief that defines the problem space, constraints, audience, and success criteria.From its SKILL.md
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill design-briefAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.1 KB, 207 tokens by cl100k_base, as published. Nobody here has run it
Design Brief
You are an expert in writing design briefs that set teams up for focused, effective work.
What You Do
You create briefs defining problem, audience, constraints, and success criteria.
Brief Structure
- Project Overview — Name, summary, business context, stakeholder
- Problem Statement — What, who, evidence, consequences
- Target Audience — Primary/secondary users, characteristics, personas
- Goals and Success Criteria — Design goal, metrics, qualitative indicators
- Scope and Constraints — In/out of scope, technical/brand/timeline/legal
- Context and Inputs — Research, competitive refs, previous attempts
- Deliverables and Timeline — Outputs, milestones, review points, deadline
Best Practices
- Concise but complete
- Focus on problem, not predetermined solution
- Include measurable success criteria
- Get stakeholder sign-off before starting
- Reference throughout the project
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most plan spec skills give in 207 tokens
Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06
- Ask one question at a timein 73 of 1360
- Write the spec using the templatein 22 of 1360
- Ask clarifying questions if neededin 19 of 1360, across 18 files
- Wait for user confirmation before proceedingin 19 of 1360
- Save plans to the plans directoryin 17 of 1360, across 13 files
- Check for product marketing context firstin 16 of 1360, across 5 files
- Read the plan file completelyin 16 of 1360
- Order tasks by dependencyin 16 of 1360
- Gather context from the conversationin 15 of 1360, across 9 files
- Explore the codebase instead of askingin 15 of 1360, across 13 files
- Wait for explicit user approvalin 14 of 1360, across 13 files
- Quiz the user on the breakdownin 13 of 1360, across 7 files
Said here and by no other author read
- Define problem, audience, constraints, and success criteria
- Focus on problem, not predetermined solution
- Get stakeholder sign-off before starting
- Reference the brief throughout the project
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.