Run upstream brand discovery covering audience research, competitive landscape, category dynamics, problem space, and positioning territory exploration. Use this skill at the very start of a brand or website project when the user needs to understand who they're for, who they compete with, what the audience actually needs, and where the brand could plausibly stand. Triggers on brand discovery, audience research, market research, competitive scan, category research, customer research, who is this for, who are we, positioning research, intake, kickoff. Also triggers when a creative brief is requested but the upstream inputs (audience, competitors, problem space) are not yet clear.
5k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
512
stars on the repo
on the repository, not the skill itself
Install
one command, takes just this skill from the repository
Upstream of every brief, identity, and content plan. Discovery answers four questions: who the brand is for, what they need, who else is competing for that need, and where the brand could plausibly stand that competitors do not.
When to use
The very first phase of a new brand or website project
Understanding an audience before any creative work begins
Mapping competitors and category dynamics
Surfacing the problem space the brand will operate in
Generating positioning territories before brief or ideation
When a creative brief was requested but the inputs are missing
When NOT to use
The audience and category are already well-understood (jump to creative-brief or brand-ideation)
Validating a specific design or feature with users (use usability-testing)
Mapping the customer journey of an existing audience (use journey-mapping)
Generating brand names or visual directions (use brand-ideation)
Required inputs
The product, service, or organization being branded
Whatever is already known about the audience and category (often very little)
Access to existing materials (sales calls, support tickets, reviews, analytics)
Any constraints (parent brand, regulatory, geographic)
A timeline (a 1-week discovery looks different than a 6-week one)
The framework: 4 dimensions
Discovery covers four dimensions. Each has its own sources, methods, and outputs.
1. Audience
Who specifically does this serve?
Layers to surface:
Demographic: Age range, geography, language, life stage, income (only if relevant; do not over-collect demographics)
Their content and SEO presence (use seo-competitor for the search angle)
Social proof and customer voices
Competitive scan benefits from quantitative grounding: not just "who are the competitors" but "how much traffic do they earn, where does it come from, who is the audience overlap." Similarweb is the standard for this kind of competitive landscape analysis; pair with Ahrefs for the SEO-specific overlap.
Output: Competitor matrix (3 to 8 competitors deep), plus a one-line "what makes them dangerous" for each.
3. Category and problem space
What is the broader context this brand operates in?
Map:
The problem. What is the actual user problem? Not the surface symptom, the underlying job to be done.
The category. How is the category structured? Is it new, mature, fragmenting, consolidating?
The conventions. What does every brand in the category do the same way? (These are the conventions you can break.)
The shifts. What is changing in the category? Technology, regulation, audience behavior, distribution.
The moats. What protects incumbents? Brand, distribution, network effects, switching costs?
The vocabulary. What language does the category use? What is jargon, what is meaningful, what is empty?
Sources:
Industry reports and analyst coverage
Trade publications and conferences
Adjacent category observations
Customer language vs. category language (the gap is informative)
Output: A category map and a list of conventions to consider breaking (or keeping deliberately).
4. Positioning territory
Given the audience, competitors, and category, where could this brand plausibly stand?
This is not yet "the positioning." Discovery surfaces possible territories. brand-ideation narrows them and commits.
Territory generation. 3 to 5 plausible positioning territories.
Write the discovery report. Use the template in references/discovery-report-template.md.
Hand off to next phase. Discovery feeds into creative-brief, brand-ideation, or content-strategy depending on where the project goes next.
Failure patterns
Skipping discovery to "save time." Every shortcut here costs 10x downstream when the brand fails to land.
Audience research that confirms what you already believe. If your audience research validates every assumption, you did not actually research. Look for surprises.
Demographic-heavy audience profiles. "Women aged 25 to 45" is not insight. Behavior, beliefs, and jobs-to-be-done are.
Listing every competitor as if equal. Most competitors do not matter. Pick the 3 that are genuinely dangerous.
Forgetting status-quo as competition. The biggest competitor is usually "doing nothing" or "doing it manually."
Outputting territories without rejection criteria. A territory without a "what this rejects" is not a territory.
Treating discovery as a one-time event. Categories shift. Audiences evolve. Re-run discovery at least every 3 years.
Output format
Default output is a discovery report at discovery-report.md plus appendices.
Structure:
Executive summary (5 to 10 bullets)
Audience (1 to 3 named segments with profiles)
Competitors (matrix and per-competitor analysis)
Category and problem space
Positioning territories (3 to 5 candidates)
Implications and recommendations
Open questions that require further research
Appendices:
Interview notes (sanitized)
Competitor research data
Source list
Reference files
references/discovery-report-template.md - Full discovery report template.
references/interview-guide.md - Audience interview guide with question prompts.
How to use it
Copy the folder
Take rampstackco/brand-discovery from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
Check the name does not clash
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.