Brand Marketing Strategy Domain

Problem Addressed

Brand marketing analysis often stops at model filling: SWOT, PESTEL, and AARRR are completed section by section, but the output does not explain which tasks depend on which, which conclusions require data evidence, or how strategy maps into ownership and iteration. Without a stable task catalog and explicit constraints, model outputs become isolated paragraphs rather than inputs to an analysis pipeline, accountability structure, and improvement loop.

How It Works

Marketing Strategy Domain is a domain payload for Universal Task OS in brand marketing. It does not provide an execution framework; it provides the “what” and “what it looks like” that UTOS can consume. Key content includes:
- Task catalog and dependency topology: covering S1 environment diagnosis, S2 competitive strategy, S3 brand positioning, S4 marketing mix, S5 growth engine, S6 consumer insight, S7 performance measurement, S8 execution management, and S9 sales monetization.
- Analysis model requirements: defining required components, assembly order, and constraints for PESTEL, Porter’s Five Forces, SWOT, Kapferer, value proposition canvas, STP, AARRR, HEART, and OKR tasks.
- Exemplar index: most exemplars are currently marked [to be filled]; users must add sanitized examples under references/exemplars/, register them by task ID, and write feature summaries before UTOS can use them as sample inputs.

At runtime, the skill checks for and loads universal-task-os. After confirming the target task type, it reads the task catalog, model requirements, and exemplar index, then delegates execution to UTOS using catalog-based method, sample-based method, and pipeline orchestration. The core constraint is that conclusions must be supported by data; major decisions require cross-validation across multiple models, and strategy must be separated into short-, medium-, and long-term horizons.

Boundaries and Notes

The skill has a hard dependency on UTOS. Without UTOS, it only supports read-only lookup of task catalogs, model requirements, and exemplar indexes; it should not generate marketing strategy, analysis reports, or execution pipelines. Because the exemplar library is incomplete, tasks that rely on sample-based reasoning require user-supplied sanitized cases. It fits structured marketing decisions in B2B, B2C, SaaS, and fast-moving consumer goods contexts, but it does not replace CRM, BI dashboards, or marketing automation platforms.