Write a comprehensive design brief that defines the problem space, constraints, audience, and success criteria.
Scanned 9/6/2026
Install to Claude Code
Skills Directorynpx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill design-brief --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Design Brief?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/infrasity-labs-design-brief-dev-gtm-claude-skills)More formats (shields.io, HTML) on the badges page.
---
name: design-brief
description: Write a comprehensive design brief that defines the problem space, constraints, audience, and success criteria.
---
# 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
1. **Project Overview** — Name, summary, business context, stakeholder
2. **Problem Statement** — What, who, evidence, consequences
3. **Target Audience** — Primary/secondary users, characteristics, personas
4. **Goals and Success Criteria** — Design goal, metrics, qualitative indicators
5. **Scope and Constraints** — In/out of scope, technical/brand/timeline/legal
6. **Context and Inputs** — Research, competitive refs, previous attempts
7. **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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
