Brand Strategy

Before final delivery of a substantive authored, revised or generated creative artifact, automatically apply output review. Reuse domain QA in one bounded loop; inspect actual media, preserve accepted locks and stop unchanged on a pass. This does not run for greetings, menus or onboarding questions. When Superpowers is in the skill list, load superpowers:systematic-debugging before diagnosing a reproducible technical defect and superpowers:verification-before-completion before calling a deliverable ready; Studio keeps ownership.

Read Studio integration authority before this method. It defines the active owner map, host capability rules and exceptions to the repository’s installation conventions. For substantive creative work, apply the conditional Research gate and search only when one of its triggers applies; purely mechanical state or packet maintenance uses its documented exemptions. Scale the artifact to the requested stage. Quick pitches remain short; known intent and valid scoped authorization do not need repeated confirmation.

Use this skill to plan brand positioning, audience fit, asset matrices, channel adaptation, non-commerce campaign or launch planning, and campaign QA without locking final creative execution too early. Offers and product, store or marketplace launches go to Sales Campaign Strategy.

For a website/store-led commercial campaign, use the website-to-campaign profile. Supply only missing brand foundations to the existing Sales Campaign Strategy's pack: source-based diagnosis, positioning, buying situations, differentiation/proof and voice. Reuse accepted strategy, inspect accessible website facts before questioning and ask one material missing question per response. Do not create duplicate plans or expand brand-only work into a campaign.

Positioning and audience research

Before writing positioning, audiences or a campaign thesis that is not already supplied and approved, follow the positioning and audience research method: the questions in order, an evidence ledger whose status decides what copy may use, audiences as situations, a tested positioning statement and a message hierarchy built from the ledger.

Brand voice guide

When the user asks for a brand voice or tone of voice guide, or a client's copy keeps drifting, write it with the brand voice guide: traits with their limits, fixed choices (form of address, name and declension, numbers), words to use and avoid, channel rhythm and before-and-after examples. Save the fixed choices into the client's brand kit.

Language Policy

Use the user’s working language; keep exact copy and requested prompt language separate. Do not infer language or onboarding status from copied source instructions.

Brand strategy and identity

For brand strategy or identity foundations, use the brand identity profile. Produce a Brand Strategy with sourced/user-supplied facts, proposed positioning, audience/use situations, differentiation and proof limits, values, voice principles and the visual direction basis. Reuse known inputs and ask exactly one missing question per response. Hand the strategy revision and selected direction to Graphic Design. Do not force campaign-only CTA, launch or asset-matrix fields into brand-only work. For campaign work, use the method below.

When To Use

Use this skill when:

• A request needs campaign logic before visual direction, copy, storyboard, or prompts.
• The user asks for brand, social, creator or promotional workflow planning without a store, product or offer goal; those go to Sales Campaign Strategy.
• Audiences, channels, claims, or asset variants need structure without a commerce goal.

Do not use this skill to invent evidence, write final copy, produce final prompts, or execute media tools.

Inputs

Required:

• brief_contract: objective, audience, deliverables, constraints, and acceptance criteria.
• offer_or_subject: product, service, idea, event, or asset focus.
• channel_context: social, email, video, static campaign, or mixed rollout (store and marketplace campaigns go to Sales Campaign Strategy).

Optional:

• proof_points: verified claims, benefits, objections, or differentiators.
• reference_pack: positioning, competitor, style, or source references.
• copy_constraints: required CTA, legal wording, tone, or banned claims.

Outputs

Produce a Marketing Plan with:

• audience and message framing
• campaign thesis and message hierarchy
• asset matrix and channel variants
• CTA system
• proof and claim boundaries
• launch or rollout notes
• QA criteria for downstream creative roles

Process

1. Clarify what the campaign must make the audience do or understand.
2. Separate verified claims from speculative messaging.
3. Map asset variants to channel jobs.
4. Define CTA and message hierarchy before visual execution.
5. Hand off to direction, copy, or storyboard roles.

Decision Rules

• For content series, launch sequences, CTAs by audience temperature, discovery calls, objection answers and follow-up, use the shared script and campaign patterns.

• Keep claims evidence-backed or label them as assumptions.

• Prefer channel-specific variants over generic reuse.

• If audience or offer is unclear, route back to brief-architect.

• If proof is missing, avoid strong performance or outcome claims.

Guardrails

• Do not fabricate testimonials, metrics, guarantees, certifications, or reviews.
• Do not execute media generation or choose external providers.
• Do not turn marketing strategy into final prompt language.
• Do not use private customer examples unless supplied for the task.

Handoff

Review gate: direction_fit when passed into creative direction.

Hand off to static-direction, motion-direction, copy-voice, or storyboard-architect with:

• campaign_thesis
• audience_offer_fit
• asset_matrix
• message_hierarchy
• claim_boundaries

QA Checklist

• Audience, offer, and channel are aligned.
• Claims are supported or labeled.
• Asset matrix matches the requested rollout.
• CTA system is clear.
• Downstream roles receive constraints, not vague inspiration.