rampstackco/claude-skills / skills/brand-discovery
brand-discovery
VerifiedRun 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.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 356 B |
| SKILL.md | skill md | 9.5 KB |
| references/discovery-report-template.md | markdown | 4.5 KB |
| references/interview-guide.md | markdown | 6.8 KB |
references/discovery-report-template.md
View on GitHub# Brand Discovery Report Template
A fillable template for the discovery deliverable. The discovery report is what every later phase of brand work references. If a section is thin, later phases will be too.
Fill every section. If a section is "N/A", say why explicitly.
---
## Project metadata
**Brand / project:** [Name]
**Phase:** [Initial discovery / refresh / repositioning]
**Date:** [YYYY-MM-DD]
**Lead:** [Name]
**Stakeholders interviewed:** [Names and roles]
**Customers interviewed:** [Number, segments]
---
## Executive summary
Three to five sentences. The single most important thing the discovery surfaced, the strongest opportunity, and the biggest risk.
> [Summary]
---
## Audience
### Primary audience
**Who they are:** [Demographic and behavioral picture. Not a persona archetype. Real, specific, current.]
**What they want:** [The job they hire the category to do. Surface and underlying.]
**What they fear or doubt:** [Objections, hesitations, alternative options being considered.]
**Where they are:** [Channels, communities, sources of trust.]
**Quotes (verbatim from interviews):**
> "[Verbatim quote that reveals motivation or pain]" - [Segment]
> "[Verbatim quote]" - [Segment]
> "[Verbatim quote]" - [Segment]
### Secondary audience(s)
[Only include if they materially shape the work. Otherwise note "none material" and move on.]
---
## Category and competition
### The category as the audience sees it
What the audience calls this category. What they group us with. (Often different from how the company sees it.)
### Direct competitors
| Competitor | Position they hold | Strength | Weakness | Opportunity for us |
|---|---|---|---|---|
| | | | | |
| | | | | |
| | | | | |
### Indirect / adjacent
[Substitutes the audience considers, even if not in the same product category.]
### Reference brands (aspirational)
[Brands the audience admires that we want to be associated with - same audience, different category.]
---
## Positioning territory
### What we found
The discovery process should produce 2 to 4 candidate positioning territories. Each is a defensible space the brand could own.
#### Territory 1: [Name]
- **Core idea:** [One sentence]
- **Why it could work:** [Audience need it serves, gap in competition, asset we have]
- **Why it could fail:** [Risk, what would have to be true]
- **What it would look like:** [How marketing, product, copy would feel under this territory]
- **Evidence from research:** [Specific findings that support this]
#### Territory 2: [Name]
[Same structure]
#### Territory 3: [Name]
[Same structure]
### Recommendation
The discovery report is allowed to recommend one. Make the case. Or explicitly punt: "Run a positioning workshop with these four candidates."
---
## Brand truths
What the discovery surfaced about who this brand actually is, not what marketing has been saying.
### What is true
- [Fact about the company, founders, product, or community that is real and ownable]
- [Fact]
- [Fact]
### What is aspirational (and that is OK)
- [Thing we want to be that we are not yet, but are credibly working toward]
- [Thing]
### What is not true (and stop saying)
- [Claim the company makes that did not survive scrutiny]
- [Claim]
---
## Strategic implications
What the discovery means for the work ahead.
### For brand identity
- [Implication, e.g., "The visual direction should signal quietness, not loudness; the audience is exhausted by category noise."]
### For brand voice
- [Implication, e.g., "Voice should be confident without being clever; the audience equates cleverness with sales pressure."]
### For product
- [Implication if discovery surfaced product-level gaps or strengths]
### For marketing
- [Implication for channel strategy, content focus, message hierarchy]
---
## Open questions
Things discovery raised that it did not answer. These belong in the next phase.
- [ ] [Question]
- [ ] [Question]
- [ ] [Question]
---
## Methodology and sources
- **Stakeholder interviews:** [Number, role mix, format]
- **Customer interviews:** [Number, segment mix, format]
- **Customer surveys:** [Sample size, response rate]
- **Competitive scan:** [Number of brands, depth of review]
- **Search and social listening:** [Sources, time window]
- **Internal docs reviewed:** [Strategy decks, prior research]
- **Caveats:** [What this discovery did not cover, sample limitations]
---
## Sign-off
Discovery accepted by:
- [Name, role, date]
- [Name, role, date]
Recommended next phase: [Brand ideation / positioning workshop / direct to identity / etc.]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |