9thlevelsoftware/legion/marketing-workflows

Marketing Workflows

Structured marketing campaign engine for Legion. Provides domain-specific decomposition for marketing-focused phases — campaign planning with guided questioning, content calendar generation, and cross-channel coordination across 8 marketing specialist agents. All operations produce human-readable markdown artifacts at .planning/campaigns/.

References:

• State File Locations from workflow-common.md (state paths, degradation pattern)
• Marketing Workflow Conventions from workflow-common.md (lifecycle, paths, wave pattern)
• Marketing Campaign team assembly from agent-registry.md Section 4 (Strategy + Content + Channel specialists)
• Phase decomposition from phase-decomposer.md (marketing domain detection trigger)
• /legion:plan in plan.md (campaign questioning and document generation entry point)
• /legion:build in build.md (marketing wave execution with core messaging handoff)

Section 1: Principles & Marketing Domain Detection

Core rules governing marketing workflows and the detection heuristic that determines when marketing-specific decomposition activates.

Principles

1. Marketing-first decomposition -- when a marketing phase is detected, use marketing-specific wave patterns (Strategy, Creation, Distribution) rather than generic engineering patterns (Build, Test, Deploy). Marketing tasks are not code tasks.
2. Human-readable artifacts -- campaign documents follow the same structured markdown convention as STATE.md, ROADMAP.md, and all other Legion state files. No JSON, no binary, no databases.
3. Graceful degradation -- every consumer checks for marketing phase signals before applying marketing patterns. Non-marketing phases see zero impact. Campaign documents are never required for non-marketing workflow completion.
4. Channel-driven team assembly -- the user's channel selection drives which agents are assigned. Not all 8 marketing agents are needed for every campaign. A 2-channel campaign gets 3-4 agents; a 5-channel campaign gets 6-7.
5. Core message consistency -- all channel agents work from a single core messaging brief produced in Wave 1. Consistency is structural (shared input), not manual (per-channel review).
6. Content templates, not content -- calendars and plans specify content types, themes, and responsible agents. Actual content creation happens during execution (Wave 2), not during planning.

When Marketing Workflows Apply

Marketing-specific decomposition activates when ANY of the canonical triggers below matches — no other triggers. Keyword matches against the phase description are NOT authoritative (they may be used as a non-blocking hint to prompt the user, never as automatic activation).

Canonical triggers (mirror of `workflow-common/SKILL.md` § Marketing Phase Detection):

1. At least one phase requirement ID matches the regex ^MKT-\d+ in ROADMAP.md or REQUIREMENTS.md
2. The phase's CONTEXT.md YAML frontmatter declares workflow_type: marketing
3. The user passed --domain=marketing to /legion:plan

Single source of truth for keywords: .planning/config/intent-teams.yaml under teams.marketing.keywords[]. Keywords are used only as prompt hints, never for silent activation. When adding a keyword, edit the YAML — do NOT inline keyword lists in this file.

When detected: use marketing-specific wave patterns (Section 6) and offer campaign document generation during planning. When not detected: standard phase decomposition applies -- no impact.

Constants

CAMPAIGN_DIR = '.planning/campaigns'
CAMPAIGN_FILE_PATTERN = '{CAMPAIGN_DIR}/{campaign-slug}.md'
DEFAULT_CHANNELS = ['twitter', 'instagram', 'tiktok', 'reddit', 'blog', 'email']
CONTENT_TYPES = ['social-post', 'thread', 'reel', 'story', 'blog-post', 'email',
                 'video-script', 'infographic', 'ama', 'poll']

Channel-Agent Mapping

Graceful Degradation

• If .planning/campaigns/ directory does not exist: create it when the first campaign is planned
• If no campaign document exists for a phase: standard decomposition, no marketing enrichment
• If marketing-workflows skill is referenced but phase is not marketing: skip silently
• Never error, never block, never require campaign documents for non-marketing workflow completion

Section 2: Campaign Planning Workflow (MKT-01)

Structured campaign creation with guided questioning, document generation, agent team assembly, and lifecycle management. This section drives the campaign planning flow triggered by /legion:plan when a marketing phase is detected.

2.1: Campaign Brief Questioning

When a marketing phase is detected during /legion:plan, gather campaign parameters using AskUserQuestion. This replaces the generic decomposition questioning for marketing phases.

Key questions (adapt based on responses -- do not ask all if answers imply others):

Q1: "What's the primary objective for this campaign?"
  Options:
  - "Brand awareness / Launch announcement"
  - "User acquisition / Growth"
  - "Community building / Engagement"
  - "Product promotion / Conversion"
 
Q2: "Who is your target audience?"
  Free text -- capture demographics, interests, platforms they use
 
Q3: "Which channels should we target?" (multi-select)
  Options from DEFAULT_CHANNELS, filtered to those with available agents
  Show the Channel-Agent Mapping so the user knows who handles each
 
Q4: "What's the campaign timeline?"
  Options:
  - "Sprint (1-2 weeks)" -- high intensity, few channels
  - "Standard (4-6 weeks)" -- full campaign cycle
  - "Ongoing (3+ months)" -- sustained presence
 
Q5: "What's the key message or value proposition?"
  Free text -- this becomes the core message for cross-channel coordination (Section 4)

If the user has already provided campaign details in the phase description or CONTEXT.md, extract answers from existing context rather than re-asking. Only ask for missing parameters.

2.2: Campaign Document Generation

After brief questioning, generate the campaign document at: {CAMPAIGN_DIR}/{campaign-slug}.md

The slug is derived from the campaign name: lowercase, spaces to hyphens, strip non-alphanumeric (except hyphens), max 40 characters. Example: "Product Launch Q2" becomes product-launch-q2

Use the format from Section 5. Populate all sections from the brief answers:

• Objectives: from Q1 + follow-up specifics
• Target Audience: from Q2
• Channel Strategy: from Q3 + Channel-Agent Mapping (Section 1)
• Core Messaging: from Q5
• Timeline: from Q4 + default phase structure for the selected pattern
• Content Calendar: generate using Section 3 patterns
• Agent Assignments: from channel selection + agent-registry Section 4 Marketing Campaign team

2.3: Agent Team Assembly

For marketing campaigns, use the agent-registry Section 4 Marketing Campaign team assembly pattern:

Required roles (always included):

Channel-specific roles (1 per selected channel):

• Map each selected channel to its primary agent using the Channel-Agent Mapping table (Section 1)
• If a channel's primary agent is already assigned as Strategy Lead or Content Lead, no duplicate -- the agent covers both roles
• Each channel specialist owns platform-native content formats for their channel

Optional roles (add based on campaign objectives):

2.4: Campaign Lifecycle

Each campaign follows this lifecycle:

Planning --> Active --> Measuring --> Complete

• Planning: Campaign document created, content calendar drafted, agents assigned. Status in campaign doc: Planning
• Active: Content being produced and distributed across channels. Status: Active
• Measuring: Campaign ended, collecting metrics and learnings. Status: Measuring
• Complete: Final report written, outcomes recorded to memory (if memory layer active). Status: Complete

Campaign status is tracked in the campaign document header, not in STATE.md. The campaign document is the source of truth for campaign lifecycle.

Section 3: Content Calendar Generation (MKT-02)

Time-based content planning with channel assignments, content type taxonomy, scheduling patterns, and assignment rules.

3.1: Calendar Structure

Content calendars live inside the campaign document (## Content Calendar section). Format is a weekly grid with channel assignments and content types.

| Week | Phase | Key Theme | Content Items |
|------|-------|-----------|---------------|
| W1 | Pre-launch | Teaser/Anticipation | Twitter thread, Instagram teaser, Blog draft |
| W2 | Launch | Core announcement | All channels: coordinated launch burst |
| W3-4 | Sustain | Engagement/Value | Regular cadence per channel |
| W5+ | Optimize | Best performers | Double down on top-performing content |

Calendar detail level: specify content TYPE and responsible AGENT per slot. Do NOT write actual content -- content creation happens during Wave 2 execution.

3.2: Content Type Taxonomy

Each content item maps to a type, channel, and responsible agent:

3.3: Scheduling Patterns

Three standard patterns based on campaign timeline (from Q4 in brief questioning):

Sprint (1-2 weeks):

• High frequency: daily content on primary channels
• Focus: 2-3 channels maximum
• Pre-create all content before launch date
• No optimization phase -- measure after sprint ends
• Best for: product launches, event promotions, time-sensitive announcements