brand-strategy-engine

Generates brand positioning, audience segmentation, and proof signals from a project design.md file.

2|Updated Jun 19, 2025
One-click install
npx skills add https://github.com/Prat05devs/dapper-city-threads --skill brand-strategy-engine-prat05devs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brand-strategy-engine
Source: https://github.com/Prat05devs/dapper-city-threads/tree/main/.agent/skills/brand-strategy-engine
Command: npx skills add https://github.com/Prat05devs/dapper-city-threads --skill brand-strategy-engine-prat05devs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into visual design, copywriting, or campaign planning without a documented strategy, producing generic output that lacks a clear audience, positioning, or proof. This Skill structures the strategic layer first so every downstream design and communication decision is grounded in confirmed or clearly marked assumptions. ## Core Features & Use Cases - Positioning Framework: Produces a positioning statement, frame of reference, points of parity, points of difference, brand promise, and proof signals. - Audience Segmentation: Defines primary and secondary audiences with their fears, goals, trusted signals, and content formats. - Department-Validated Use Cases: Builds a stakeholder table mapping use cases, required messages, approval owners, and risk levels for cross-functional brands. - Use Case: Before designing a conference website, run this Skill against the project's design.md to produce a strategy brief covering category, motive, audience tension, tone of voice, and open questions. ## Quick Start Use the brand-strategy-engine skill to build the full brand strategy from my design.md before any visual design work begins.

Frequently Asked Questions about brand-strategy-engine

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

FAQPage Schema
How do I create a brand positioning statement before designing a website?▼

Run this Skill against your project design.md to produce a positioning statement in the form: for target audience, project is a category that helps them achieve an outcome because of a key difference. It also outputs frame of reference, points of parity, and points of difference.

What inputs does a brand strategy workflow need?▼

The Skill prefers a canonical design.md file, optionally supplemented by brand-architecture.md, context-normalized.md, source-register.md, and stakeholder notes. If design.md is missing or stale, strategy work should pause until context is updated.

How do I handle unconfirmed brand assumptions in a strategy document?▼

Mark every claim with a status: confirmed for directly stated source material, inferred for reasoned conclusions, and missing for items needing user input. This prevents invented audiences, personalities, or promises from being treated as fact.

When should I use a branded house versus a house of brands?▼

Choose a single brand for one unified identity, a branded house when one parent spans departments or modules, and a house of brands only when separate identities are strategically required. The Skill marks the choice as confirmed or inferred based on project context.

What are the limitations of strategy-only brand planning?▼

This Skill produces strategy only and does not generate visual identities, logos, or verbal systems. Its output quality depends entirely on the accuracy of the input design.md, so stale or contradicted context must be resolved first.