workflow-orchestrator

PMM Workflow Orchestrator

Orchestrates multi-skill PMM programs end-to-end. Chains your existing skills, passes state between them, writes back to brain, and produces one master program document.

---

Brain Integration

This orchestrator READS from brain:

• Section 1: Product Context
• Section 2: ICP
• Section 3: Positioning (checks staleness)
• Section 4: Alternatives Map (checks gaps)
• Section 5: Proof Points
• Section 6: Voice & Tone
• Section 7: Launch History (for learning)

This orchestrator WRITES to brain:

• Updates Section 3 (after positioning refresh)
• Updates Section 4 (after competitive work)
• Updates Section 5 (after new proof points)
• Updates Section 7 (after launch or retro)

---

Supported Workflows

1. Full Product Launch Workflow

Trigger: "run full launch workflow", "launch [product]", "full GTM for [product]"

Sub-skills invoked (in order):

1. Check brain Section 3 → if stale (>6 months), run hs-positioning-messaging
2. Check brain Section 4 → if competitor mentioned or T1/T2, run hs-competitive-battlecard
3. Run hs-buyer-personas (if Section 2 incomplete or buying committee changed)
4. Run go-to-market-strategy (assigns tier, generates strategy)
5. Run hs-gaccs-brief (campaign brief)
6. Route to product-launch-playbook (if T1/T2) for detailed execution
7. Run hs-stakeholder-maps (internal alignment)
8. Set T+90 reminder for hs-retro

Duration: 6-12 weeks (T1), 4-8 weeks (T2), 2-3 weeks (T3)

Brain updates:

• Section 3: Positioning (if refreshed)
• Section 4: Competitive intel
• Section 7: Launch plan (marked "Planned")

---

2. Positioning Refresh Workflow

Trigger: "refresh positioning", "positioning workshop", "update positioning", "our messaging is stale"

Sub-skills invoked:

1. Run hs-positioning-messaging (BUILD or AUDIT mode)
2. Update brain Section 3 with new positioning
3. Run hs-value-prop-statements (generate persona-specific copy)
4. Update hs-competitive-battlecard for all competitors (competitive differentiation section)
5. Run hs-alternatives-map (if alternatives changed)

Duration: 1-2 weeks

Brain updates:

• Section 3: Positioning (full refresh)
• Section 4: Alternatives Map (if changed)

---

3. Competitive Intelligence Program

Trigger: "competitive program", "competitive deep-dive for [competitor]", "build battlecards", "competitive refresh"

Sub-skills invoked:

1. Run hs-alternatives-map (if not current)
2. For each top competitor, run hs-competitive-battlecard
3. Run hs-ci-stakeholder-briefing (generate exec-level competitive newsletter)
4. Update brain Section 4 with all competitive intel

Duration: 2-4 weeks

Brain updates:

• Section 4: Alternatives Map + all battlecards
• Section 7: Competitive program completion (track quarterly)

---

4. Quarterly PMM Cycle

Trigger: "quarterly PMM cycle", "Q[X] refresh", "quarterly review", "PMM sprint"

Sub-skills invoked:

1. Run hs-retro for all launches from previous quarter
2. Run hs-positioning-messaging (AUDIT mode → refresh if needed)
3. Run hs-competitive-battlecard (refresh top 3 competitors)
4. Run hs-proof-points-claims (audit + add new proof points)
5. Run hs-buyer-personas (update if ICP shifted)
6. Run hs-brainstorm-okrs (set next quarter OKRs)

Duration: 3-4 weeks

Brain updates:

• Section 3: Positioning (if refreshed)
• Section 4: Competitive intel (refreshed)
• Section 5: Proof points (audited + updated)
• Section 7: Quarterly retros + new OKRs

---

5. New Market Entry Program

Trigger: "enter new market", "expand to [segment]", "new vertical", "market expansion"

Sub-skills invoked:

1. Run hs-icp (define ICP for new market)
2. Run hs-buyer-personas (buying committee for new market)
3. Run hs-positioning-messaging (positioning for new segment)
4. Run hs-competitive-battlecard for top 3 competitors in that market
5. Run go-to-market-strategy (tier + strategy for market entry)
6. Run hs-gaccs-brief (campaign brief)
7. Route to product-launch-playbook for execution

Duration: 8-12 weeks

Brain updates:

• Section 2: ICP (expanded or new segment)
• Section 3: Positioning (adapted for new market)
• Section 4: Competitive landscape (new market)

---

6. Post-Launch Retrospective Workflow

Trigger: "run retro for [launch]", "post-launch review", "analyze [launch] results", "update brain after launch"

Sub-skills invoked:

1. Run hs-retro (structured retrospective with cross-functional team)
2. Update brain Section 7 with actual results vs targets
3. Flag tier calibration issues (was tier correct?)
4. Suggest adjustments for next similar launch

Duration: 1 week

Brain updates:

• Section 7: Launch entry updated from "Planned" to "Completed" with actuals

---

7. Competitive Response (Fast)

Trigger: "competitive response to [competitor]", "they just launched [feature]", "fast battlecard"

Sub-skills invoked:

1. Run hs-competitive-battlecard for that competitor (expedited)
2. Run hs-value-prop-statements (differentiation messaging)
3. Generate sales enablement assets (comparison one-pager, talk tracks)

Duration: 1-2 weeks

Brain updates:

• Section 4: Updated competitive intel for that competitor

---

8. ICP + Personas Foundation Workflow

Trigger: "define our ICP", "who should we sell to", "build personas", "buyer intelligence"

Sub-skills invoked:

1. Run hs-icp (define/pressure-test ICP)
2. Run hs-buyer-personas (buying committee + messaging personas)
3. Run hs-interview-summary for any existing customer interviews
4. Update brain Section 2 with ICP + personas

Duration: 2-3 weeks

Brain updates:

• Section 2: Complete ICP + personas

---

9. Voice & Tone Foundation Workflow

Trigger: "define our voice", "brand voice guide", "tone of voice", "our copy sounds inconsistent"

Sub-skills invoked:

1. Run hs-voice-tone (BUILD mode)
2. Update brain Section 6 with voice guide
3. Run hs-writing-assistant (test voice on sample copy)

Duration: 1 week

Brain updates:

• Section 6: Voice & Tone guide

---

10. Full PMM Onboarding (New Hire)

Trigger: "onboard new PMM", "PMM audit", "what's our current state", "I just joined as PMM"

Sub-skills invoked (read-only audit):

1. Audit brain Sections 1-7 (what's complete, what's missing, what's stale)
2. Run hs-positioning-messaging (AUDIT mode)
3. Run hs-proof-points-claims (audit current claims)
4. Run hs-competitive-battlecard (audit existing battlecards)
5. Produce "Current State" report with prioritized gaps

Duration: 1-2 weeks

Brain updates: None (read-only audit)

---

Example Prompts

Full launch:

/workflow-orchestrator "Run full launch workflow for analytics dashboard" DRI: me Timeline: 8 weeks Target: mid-market product teams Success metric: 30% adoption in 90 days

Quarterly cycle:

/workflow-orchestrator "Run Q3 quarterly PMM cycle" Include: Retro on Q2 launches, position refresh, competitive update, new OKRs

Market entry:

/workflow-orchestrator "Run market entry workflow for healthcare vertical" New segment: Healthcare Timeline: 12 weeks ICP: Health systems (100-500 bed)

Competitive response:

/workflow-orchestrator "Competitive response to Okta SSO launch" Competitor: Okta Product launched: SSO integration Urgency: High (T2/T3)

---

How It Works (Phase by Phase)

Phase 0: Program Definition

1. You name the workflow type (or describe the initiative)
2. Orchestrator clarifies:
   • DRI (directly responsible individual)
   • Timeline + deadline
   • Success criteria
   • Key stakeholders
3. Produces "Program Charter" document

Phase 1: Brain Context Check

1. Reads all brain sections
2. Flags staleness:
   • "Positioning is 8 months old" → will refresh
   • "No competitive intel for Okta" → will build
   • "ICP needs update for new segment" → will rebuild
3. Lists gaps and remediation plan

Phase 2: Skill Sequencing

1. Determines skill chain for this workflow
2. Sets input/output contracts between skills
3. Produces skill sequence diagram
4. Alerts if missing required context

Phase 3: Skill Execution

1. Invokes first skill with Program State doc
2. Each skill produces artifact + updates Program State
3. Next skill reads updated Program State
4. Continues until workflow complete

Phase 4: Cross-Skill Coherence Check

1. Verifies positioning ↔ personas consistency
2. Verifies personas ↔ proof points consistency
3. Verifies proof points ↔ competitive intel consistency
4. Flags contradictions and suggests fixes

Phase 5: Brain Update

1. Writes all artifacts back to brain
2. Updates relevant sections:
   • Section 2 (ICP/personas)
   • Section 3 (positioning)
   • Section 4 (competitive)
   • Section 5 (proof points)
   • Section 7 (launch history)
3. Timestamps each update

Phase 6: Master Program Document

1. Compiles all skill outputs into one master doc
2. Includes:
   • Program charter
   • All artifacts (positioning, battlecards, strategy, briefs, etc.)
   • Success metrics
   • Timeline + milestones
   • Open questions
   • Next steps

Phase 7: Self-Improvement Loop

1. After workflow completes, logs to brain Section 7
2. Captures: workflow type, duration, outcomes, issues
3. Future workflows reference this log for learning

---

What Makes This Different

✅ State passing: Each skill gets full context from prior skills ✅ Brain integration: Reads context once, writes back at end ✅ Coherence checking: Ensures positioning, personas, proof points align ✅ Master document: One single source of truth for entire GTM program ✅ Self-learning: Future workflows get smarter from past learnings ✅ Error handling: Flags missing context before invoking skills ✅ Flexibility: Works for any workflow (launch, refresh, new market, etc.)

---

Common Errors & Fixes

"Missing brain file" → Run product-marketing-context to set up brain first

"Positioning is stale" → Orchestrator will automatically refresh it as part of workflow

"Competitors not defined" → Orchestrator will run hs-alternatives-map first

"Tier wasn't assigned correctly" → Run go-to-market-strategy again with more context

---

Part of the PMM Go-to-Market collection. Orchestrates all PMM skills into complete GTM workflows. Reads from brain, writes back to brain after completion. Produces master program documents for GTM success.