taketomarket 0.1.0

package/workflows/discipline/seo-audit.md

@@ -0,0 +1,169 @@
+<purpose>
+Technical and content SEO audit of a URL or content. Evaluates against SEO playbook
+gate definitions and generates a structured PASS/WARN/FAIL report per check.
+Single-pass analysis workflow per D-07.
+</purpose>
+
+<required_reading>
+@${CLAUDE_PLUGIN_ROOT}/references/context-loading.md
+@${CLAUDE_PLUGIN_ROOT}/playbooks/seo.md
+</required_reading>
+
+<constraints>
+## POSITIONING.md is READ-ONLY
+
+**Do NOT modify `.marketing/POSITIONING.md` during this workflow.**
+
+POSITIONING.md is an architectural invariant. If you detect positioning drift:
+- Flag the issue and recommend running /ttm-positioning-check
+
+Only /ttm-positioning-shift and /ttm-init may modify POSITIONING.md.
+</constraints>
+
+<process>
+
+## Text-Mode Detection
+
+**Text mode (`--text` flag):** Set `TEXT_MODE=true` if `--text` is present in `$ARGUMENTS`
+or if the runtime is not Claude Code. When TEXT_MODE is active, replace every
+`AskUserQuestion` call with a plain-text numbered list.
+
+Detection:
+```bash
+if echo "$ARGUMENTS" | grep -q -- '--text'; then TEXT_MODE=true; fi
+```
+
+If `AskUserQuestion` tool is not available in the current runtime, set `TEXT_MODE=true`.
+
+---
+
+## Step 1: Load Context
+
+```
+takeToMarket > LOADING CONTEXT FOR SEO AUDIT
+```
+
+**Tier 1 summaries** (lines 1 to `<!-- END_SUMMARY -->`) from all 9 `.marketing/` reference files.
+**Tier 2 (full):** `.marketing/CHANNELS.md` (channel-specific SEO config).
+**Playbook gates:** @${CLAUDE_PLUGIN_ROOT}/playbooks/seo.md
+
+If `.marketing/POSITIONING.md` does not exist: Error and exit.
+
+---
+
+## Step 2: Get Audit Target
+
+Ask: "What would you like to audit? Provide a URL, file path, or paste content directly."
+
+Parse input:
+- **URL** (starts with `http://` or `https://`): Attempt WebFetch for page content.
+  - **WebFetch available (SEARCH_MODE=web):** Fetch and analyze.
+  - **WebFetch NOT available (SEARCH_MODE=manual):** Ask user to paste page content.
+- **File path:** Read the file directly.
+- **Pasted content:** Use directly.
+
+Store as `AUDIT_CONTENT` and `AUDIT_TARGET`.
+
+---
+
+## Step 3: Run SEO Gate Checks
+
+```
+takeToMarket > RUNNING SEO GATE CHECKS
+```
+
+Evaluate `AUDIT_CONTENT` against 8 SEO discipline gates:
+
+**1. Search Intent Match (DISC-SEO-02)**
+- PASS: Content format and opening directly match the search intent
+- WARN: Content addresses query but format is mixed or answer is buried
+- FAIL: Content format contradicts the search intent
+
+**2. Keyword Placement (DISC-SEO-01)**
+Target keyword in: title tag, H1, first 100 words, meta description, H2.
+- PASS: Keyword in title, H1, first 100 words; title 50-60 chars
+- WARN: Missing from 1-2 placements; title 45-49 or 61-70 chars
+- FAIL: Missing from title or H1; title under 30 or over 70 chars
+
+**3. Content Structure**
+Heading hierarchy (H1 > H2 > H3), no skipped levels, H2 sections 150-400 words.
+- PASS: Single H1, logical hierarchy, no skipped levels
+- WARN: Minor hierarchy issues or uneven section lengths
+- FAIL: No H1, multiple H1s, or broken hierarchy
+
+**4. Internal Linking Density (DISC-SEO-04)**
+- PASS: 3-6 internal links per 1000 words with descriptive anchors
+- WARN: 1-2 internal links per 1000 words
+- FAIL: 0 internal links
+
+**5. Schema Markup (DISC-SEO-03)**
+Article, FAQ, HowTo, or Product schema with required fields.
+- PASS: Appropriate schema type with all required fields
+- WARN: Schema present but incomplete
+- FAIL: No schema for content that qualifies
+
+**6. Entity Coverage**
+Key entities search engines associate with the topic.
+- PASS: References relevant entities (people, orgs, concepts)
+- WARN: Some coverage but missing key entities
+- FAIL: No recognizable entity references
+
+**7. Thin Content Detection (DISC-SEO-05)**
+- PASS: 800+ words standard (300+ programmatic); original analysis present
+- WARN: 500-799 words; mostly summarized
+- FAIL: Under 500 words; boilerplate content
+
+**8. Core Web Vitals Budget (DISC-SEO-07)**
+- PASS: Optimized images with dimensions, lazy-load, no render blockers
+- WARN: Images missing dimensions or unoptimized formats
+- FAIL: Heavy unoptimized media or render-blocking embeds
+
+Per check: assign PASS / WARN / FAIL with specific evidence.
+
+---
+
+## Step 4: Generate Report
+
+Display structured report:
+```
+========================================
+takeToMarket > SEO AUDIT REPORT
+========================================
+Target: [URL or filename]
+Date: [current date]
+Overall: [X/8 PASS] [Y/8 WARN] [Z/8 FAIL]
+
+| # | Gate                   | Result | Evidence              |
+|---|------------------------|--------|-----------------------|
+| 1 | Search Intent Match    | [P/W/F] | [brief evidence]     |
+| 2 | Keyword Placement      | [P/W/F] | [brief evidence]     |
+| 3 | Content Structure      | [P/W/F] | [brief evidence]     |
+| 4 | Internal Linking       | [P/W/F] | [brief evidence]     |
+| 5 | Schema Markup          | [P/W/F] | [brief evidence]     |
+| 6 | Entity Coverage        | [P/W/F] | [brief evidence]     |
+| 7 | Thin Content Detection | [P/W/F] | [brief evidence]     |
+| 8 | Core Web Vitals Budget | [P/W/F] | [brief evidence]     |
+
+FINDINGS (WARN/FAIL details):
+- [Gate]: [Issue and recommendation]
+
+RECOMMENDATIONS (priority-ordered):
+1. [Highest-impact fix]
+2. [Next priority]
+```
+
+---
+
+## Step 5: Completion
+
+```
+========================================
+takeToMarket > SEO AUDIT COMPLETE
+========================================
+Target: ${AUDIT_TARGET} | Result: [X/8 PASS] [Y/8 WARN] [Z/8 FAIL]
+```
+
+Offer: "Save this report to .marketing/AUDITS/seo-audit-[date].md? (yes/no)"
+If yes: create `.marketing/AUDITS/` directory if needed and write the report.
+
+</process>

package/workflows/lifecycle/brief-positioning-check.md

@@ -0,0 +1,90 @@
+# Positioning Check Rules
+
+## Usage
+
+Referenced by `workflows/lifecycle/brief.md` via @-syntax.
+Applied after brief content is fully generated to detect positioning drift.
+This is a soft gate per D-05 -- the brief is ALWAYS generated regardless of gate result.
+Drift produces a warning, not a block.
+
+---
+
+## Check 1: Positioning Anchor Alignment
+
+**Field:** Brief's "Positioning Anchor > Key message"
+**Checks against:** POSITIONING.md primary differentiator phrase
+
+- PASS: Brief's positioning anchor restates or naturally extends the primary differentiator
+- WARN: Brief's anchor partially overlaps but introduces claims not present in POSITIONING.md
+- FAIL: Brief's anchor uses a different differentiation claim entirely
+
+**Drift detail format:** "Positioning anchor '[brief anchor]' does not align with primary differentiator '[positioning differentiator]'"
+
+## Check 2: ICP Segment Match
+
+**Field:** Brief's "ICP Segment > Primary segment"
+**Checks against:** POSITIONING.md target audience
+
+- PASS: Brief's ICP segment matches or is a sub-segment of the POSITIONING.md target audience
+- WARN: Brief targets an adjacent audience not explicitly in POSITIONING.md
+- FAIL: Brief targets a completely different audience
+
+**Drift detail format:** "ICP segment '[brief segment]' does not match target audience '[positioning audience]'"
+
+## Check 3: Proof Point Sourcing
+
+**Field:** Brief's "Proof Points" table
+**Checks against:** POSITIONING.md must-include proof points
+
+- PASS: All proof points in the brief are sourced from POSITIONING.md proof point library
+- WARN: Brief includes proof points not in the library (may be valid new evidence)
+- FAIL: Brief makes claims with no proof point sourcing at all
+
+**Drift detail format:** "Proof point '[claim]' not found in POSITIONING.md proof point library"
+
+## Check 4: Must-Not-Say Terms
+
+**Field:** Entire brief content
+**Checks against:** POSITIONING.md must-not-say terms list
+
+- PASS: No must-not-say terms found in brief
+- FAIL: One or more must-not-say terms detected
+
+**Drift detail format:** "Must-not-say term '[term]' found in brief [section]"
+
+## Check 5: Hook-Positioning Coherence
+
+**Field:** Brief's "Hook" section
+**Checks against:** POSITIONING.md primary differentiator and category
+
+- PASS: Hook reinforces the positioning -- uses aligned language and framing
+- WARN: Hook is neutral -- does not reinforce but does not contradict
+- FAIL: Hook contradicts the positioning or uses competitor framing
+
+**Drift detail format:** "Hook framing '[hook summary]' contradicts positioning category '[category]'"
+
+---
+
+## Gate Result Logic
+
+- If ALL checks PASS: gate result = "pass"
+- If ANY check is WARN or FAIL: gate result = "warn"
+- The brief is ALWAYS generated regardless of gate result (per D-05)
+
+## Drift Warning Template
+
+When gate result is "warn", insert at the TOP of BRIEF.md after the title line:
+
+```
+<!--
+!! POSITIONING DRIFT WARNING !!
+The following items may not align with your positioning:
+- [drift detail from each failing check]
+Review .marketing/POSITIONING.md and adjust the brief if needed.
+Run /ttm-positioning-check for a full audit.
+-->
+```
+
+This is an HTML comment so it is visible in source but not rendered.
+The warning uses specific drift detail format strings from each failing check
+so the user can pinpoint exactly what drifted and from what reference value.

package/workflows/lifecycle/brief.md

@@ -0,0 +1,355 @@
+<purpose>
+Campaign brief generation workflow with outcome metric enforcement (LIFE-04) and
+positioning check gate (LIFE-05). Collects all mandatory brief fields (D-07),
+validates outcome metrics with guided re-prompting (D-06), runs 5-check positioning
+gate that warns on drift without blocking (D-05), and writes the completed brief
+to CAMPAIGNS/<slug>/BRIEF.md. This is the gate between campaign planning and
+content production.
+</purpose>
+
+<required_reading>
+@${CLAUDE_PLUGIN_ROOT}/references/context-loading.md
+@${CLAUDE_PLUGIN_ROOT}/workflows/lifecycle/brief-positioning-check.md
+@${CLAUDE_PLUGIN_ROOT}/templates/campaign-brief.md
+</required_reading>
+
+<constraints>
+## POSITIONING.md is READ-ONLY
+
+**Do NOT modify `.marketing/POSITIONING.md` during this workflow.**
+
+POSITIONING.md is an architectural invariant. If you detect positioning drift:
+- In verify: use the Escalate option to launch /ttm-positioning-shift
+- In other workflows: flag the issue and recommend running /ttm-positioning-check
+
+Only /ttm-positioning-shift and /ttm-init may modify POSITIONING.md.
+</constraints>
+
+<process>
+
+## Text-Mode Detection
+
+**Text mode (`--text` flag):** Set `TEXT_MODE=true` if `--text` is present in `$ARGUMENTS`
+or if the runtime is not Claude Code. When TEXT_MODE is active, replace every
+`AskUserQuestion` call with a plain-text numbered list.
+
+Detection:
+```bash
+if echo "$ARGUMENTS" | grep -q -- '--text'; then TEXT_MODE=true; fi
+```
+
+If `AskUserQuestion` tool is not available in the current runtime, set `TEXT_MODE=true`.
+
+When TEXT_MODE is active, replace each AskUserQuestion with a plain-text numbered list:
+```
+[HEADER]
+[QUESTION]
+  1. [OPTION_1_LABEL] -- [OPTION_1_DESCRIPTION]
+  2. [OPTION_2_LABEL] -- [OPTION_2_DESCRIPTION]
+  ...
+Type the number of your choice:
+```
+
+For multiSelect questions, instruct the user: "Type the numbers of your choices separated by commas (e.g., 1,3,5):"
+
+---
+
+## Step 1: Load Context
+
+```
+takeToMarket > LOADING CONTEXT
+```
+
+Extract SLUG from $ARGUMENTS (strip `--text` flag if present):
+```bash
+SLUG=$(echo "$ARGUMENTS" | sed 's/--text//g' | xargs)
+```
+
+Read Tier 1 summaries from all 9 reference files (lines 1 to `<!-- END_SUMMARY -->`):
+- `.marketing/POSITIONING.md`
+- `.marketing/BRAND.md`
+- `.marketing/ICP.md`
+- `.marketing/CHANNELS.md`
+- `.marketing/STATE.md` (frontmatter only)
+- `.marketing/CALENDAR.md`
+- `.marketing/COMPETITORS.md`
+- `.marketing/METRICS.md`
+- `.marketing/LEARNINGS.md`
+
+Read Tier 2 (full content) for:
+- `.marketing/ICP.md`
+- `.marketing/CHANNELS.md`
+- `.marketing/METRICS.md`
+- `.marketing/CALENDAR.md`
+
+Read full `.marketing/POSITIONING.md` (needed for positioning check gate in Step 6).
+
+Read campaign-specific files (always full-load per context-loading.md rule 4):
+- `.marketing/CAMPAIGNS/${SLUG}/STATE.md`
+- `.marketing/CAMPAIGNS/${SLUG}/RESEARCH.md`
+
+---
+
+## Step 2: Validate Campaign and Phase Order (per D-08)
+
+Check campaign exists:
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" campaign state "${SLUG}" --raw
+```
+
+If result shows `exists: false`: Tell the user the campaign does not exist and suggest running `/ttm-new-campaign` first. Exit.
+
+Read campaign state. Check the `phase` field:
+
+- If phase is `"created"`:
+  Warn the user:
+  "Research not yet completed for this campaign. Brief quality will be limited without research data. Run `/ttm-research ${SLUG}` first for better results. Proceed without research?"
+  Wait for user confirmation. If user declines, exit.
+
+- If phase is NOT `"created"` and NOT `"researched"`:
+  Warn the user:
+  "Campaign is in phase `${PHASE}`. Expected 'researched' before briefing. Running /ttm-brief now will overwrite the existing BRIEF.md. Proceed?"
+  Wait for user confirmation. If user declines, exit.
+
+Check if RESEARCH.md has actual content (not just template placeholders):
+- Read `.marketing/CAMPAIGNS/${SLUG}/RESEARCH.md`
+- If file contains only `[GENERATED BY /ttm-research]` placeholders: set `RESEARCH_AVAILABLE=false`
+- If file has real content beyond placeholders: set `RESEARCH_AVAILABLE=true`
+
+---
+
+## Step 3: Outcome Metric Enforcement (per D-06, LIFE-04)
+
+```
+takeToMarket > GENERATING BRIEF
+```
+
+**Collect campaign goal:**
+
+Ask (freeform, NOT AskUserQuestion):
+"What is the goal of this campaign? (One sentence describing the campaign's purpose)"
+
+Store the response as `CAMPAIGN_GOAL`.
+
+**Collect outcome metric:**
+
+Ask (freeform):
+"What is the outcome metric for this campaign? An outcome metric measures a business result, not an output action.
+
+Examples:
+  - VALID: 'Increase trial signups by 20% within 30 days'
+  - VALID: 'Generate 50 qualified leads from organic search in Q2'
+  - NOT VALID: 'Publish 4 blog posts' (this is an output, not an outcome)
+
+What business outcome will this campaign drive?"
+
+**Validate the response:**
+
+- FAIL if metric starts with output verbs: publish, write, send, create, post, design, build, launch (without a measurable outcome attached)
+- FAIL if no target value (number, percentage, or specific benchmark) is present
+- FAIL if no measurement window (timeframe) is present
+
+**On FAIL (retry 1):** Re-prompt with explanation:
+"That looks like an output metric, not an outcome. An output is what you produce (blog posts, emails). An outcome is the business result (signups, revenue, leads). Please provide: [specific business outcome] + [target value] + [measurement window]"
+
+**On FAIL (retry 2):** Re-prompt once more with different framing:
+"I still need a measurable business outcome. Think about what changes in your business AFTER the content is published. Example: 'Increase demo requests by 15% within 60 days of launch.' What business result are you targeting?"
+
+**After 2 failed retries:** Block brief generation entirely. Tell user:
+"Cannot generate a brief without a valid outcome metric. A brief without a measurable business outcome would produce untestable content. Run `/ttm-brief ${SLUG}` again when ready."
+Exit.
+
+**On PASS:** Store as `OUTCOME_METRIC`. Extract `target_value` and `measurement_window` from the response.
+
+**Collect output metric:**
+
+Ask (freeform):
+"What are the output metrics? (Assets and volume to produce, e.g., '4 blog posts, 2 emails, 1 landing page')"
+
+If the user provides an empty response or declines: set `OUTPUT_METRIC_MISSING=true`. Continue. This is allowed per D-06.
+
+---
+
+## Step 4: Collect Remaining Brief Fields (per D-07)
+
+**ICP Segment:**
+Read the primary segment from `.marketing/ICP.md` Tier 1 summary. Present it to the user:
+"Your primary ICP segment is: [segment from ICP.md]. Is this correct for this campaign, or are you targeting a specific sub-segment?"
+Store the confirmed or adjusted segment as `ICP_SEGMENT`.
+
+**Channel Mix:**
+Read active channels from `.marketing/CHANNELS.md`.
+
+Use AskUserQuestion (or text-mode numbered list) with `multiSelect=true`:
+- header: "Channel Selection"
+- question: "Which channels will this campaign use?"
+- options: One option per active channel from CHANNELS.md
+
+After selection, for each selected channel ask:
+"What is the role of [channel] in this campaign? (primary / support / amplification)"
+Store channel selections with roles as `CHANNEL_MIX`.
+
+**Hook:**
+If `RESEARCH_AVAILABLE=true`: Present key findings from RESEARCH.md (ambient narrative, content gaps) and suggest hook angles based on them.
+Ask: "What is the opening angle or attention-capture strategy for this campaign?"
+Store as `HOOK`.
+
+**Proof Points:**
+Read proof points from `.marketing/POSITIONING.md` Proof Point Library table.
+Display the available proof points. Ask:
+"These are your approved proof points. Do you want to add any campaign-specific claims or evidence?"
+Store base proof points plus any additions as `PROOF_POINTS`.
+
+**Timeline:**
+Ask: "What is the target ship date for this campaign?"
+Derive remaining timeline dates backward from the ship date:
+- Brief complete: today
+- Production start: ship date minus appropriate buffer
+- Review complete: ship date minus review buffer
+- Measurement start: ship date
+- Learn review: ship date + measurement window
+Store as `TIMELINE`.
+
+**Success Criteria:**
+Ask: "What specific, measurable outcomes define success for this campaign beyond the outcome metric?"
+Store as `SUCCESS_CRITERIA`.
+
+**Failure Criteria:**
+Ask: "What conditions should trigger a campaign pause or kill?"
+Store as `FAILURE_CRITERIA`.
+
+---
+
+## Step 5: Generate BRIEF.md
+
+Read the brief template:
+```
+${CLAUDE_PLUGIN_ROOT}/templates/campaign-brief.md
+```
+
+Fill ALL `[GENERATED BY /ttm-brief]` placeholders with collected data:
+
+- **Campaign Name:** From campaign STATE.md `name` field
+- **Goal:** From `CAMPAIGN_GOAL`
+- **Outcome Metric section:**
+  - Metric: `OUTCOME_METRIC`
+  - Target value: extracted `target_value`
+  - Measurement window: extracted `measurement_window`
+  - Data source: inferred from metric type or ask user
+- **Output Metric section:** From output metrics collected in Step 3
+  - If `OUTPUT_METRIC_MISSING=true`, insert after the Output Metric section:
+    `<!-- OUTPUT_METRIC_MISSING: Add output metrics before /ttm-produce -->`
+- **ICP Segment:** From `ICP_SEGMENT` (Step 4)
+- **Positioning Anchor:**
+  - Key message: derived from POSITIONING.md primary differentiator, adapted for campaign
+  - Primary differentiator: quoted directly from POSITIONING.md
+- **Hook:** From `HOOK` (Step 4)
+- **Proof Points table:** From `PROOF_POINTS` -- POSITIONING.md proof library + campaign additions
+- **Channel Mix table:** From `CHANNEL_MIX` with roles (Step 4)
+- **Assets List table:** Derived from output metrics + channel mix
+- **Success Criteria:** From `SUCCESS_CRITERIA` (Step 4)
+- **Failure Criteria:** From `FAILURE_CRITERIA` (Step 4)
+- **Dependencies:** Inferred from campaign context (reference files, tools, approvals needed)
+- **Timeline table:** From `TIMELINE` (Step 4)
+
+Store the generated content as `BRIEF_CONTENT`.
+
+---
+
+## Step 6: Positioning Check Gate (per D-05, LIFE-05)
+
+```
+takeToMarket > POSITIONING CHECK
+```
+
+Read the positioning check rules from `@${CLAUDE_PLUGIN_ROOT}/workflows/lifecycle/brief-positioning-check.md`.
+
+Apply all 5 checks against `BRIEF_CONTENT`:
+
+1. **Positioning Anchor Alignment:** Compare brief's "Positioning Anchor > Key message" against POSITIONING.md primary differentiator phrase. Determine PASS/WARN/FAIL.
+
+2. **ICP Segment Match:** Compare brief's "ICP Segment > Primary segment" against POSITIONING.md target audience. Determine PASS/WARN/FAIL.
+
+3. **Proof Point Sourcing:** Check each proof point in the brief against POSITIONING.md proof point library. Determine PASS/WARN/FAIL.
+
+4. **Must-Not-Say Terms:** Scan entire brief content for any terms from POSITIONING.md must-not-say list. Determine PASS/FAIL.
+
+5. **Hook-Positioning Coherence:** Compare brief's hook against POSITIONING.md primary differentiator and category. Determine PASS/WARN/FAIL.
+
+**Determine gate result:**
+- If ALL checks PASS: gate result = `"pass"`
+- If ANY check is WARN or FAIL: gate result = `"warn"`
+
+**If gate result is "warn":** Insert the drift warning HTML comment block at the top of BRIEF_CONTENT, after the title line. List each specific drift item using the drift detail format string from the check rules:
+
+```
+<!--
+!! POSITIONING DRIFT WARNING !!
+The following items may not align with your positioning:
+- [drift detail from each failing check, using format strings from brief-positioning-check.md]
+Review .marketing/POSITIONING.md and adjust the brief if needed.
+Run /ttm-positioning-check for a full audit.
+-->
+```
+
+The brief is written unconditionally. NEVER block brief generation on positioning drift (per D-05).
+
+---
+
+## Step 7: Write BRIEF.md and Update State
+
+Write `BRIEF_CONTENT` to `.marketing/CAMPAIGNS/${SLUG}/BRIEF.md`.
+
+Update campaign state:
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" campaign update "${SLUG}" phase briefed
+TIMESTAMP=$(node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" timestamp --raw)
+if [ -z "$TIMESTAMP" ]; then
+  echo "Error: could not get timestamp"; exit 1
+fi
+node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" campaign update "${SLUG}" phase.briefed "$TIMESTAMP"
+node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" campaign update "${SLUG}" gate.outcome_metric pass
+node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" campaign update "${SLUG}" gate.positioning_check [pass|warn]
+```
+
+Replace `[pass|warn]` with the actual gate result from Step 6.
+
+---
+
+## Step 8: Display Summary
+
+```
+takeToMarket > BRIEF COMPLETE
+
+Brief saved to .marketing/CAMPAIGNS/${SLUG}/BRIEF.md
+
+Outcome metric: [OUTCOME_METRIC]
+Positioning check: [pass|warn]
+Output metric: [defined|MISSING -- add before /ttm-produce]
+Channels: [list of selected channels]
+Assets: [count] planned
+
+[If positioning_check=warn:]
+!! Positioning drift detected -- see warning in BRIEF.md
+Review .marketing/POSITIONING.md and adjust if needed.
+
+Next: Run /ttm-produce ${SLUG}
+```
+
+</process>
+
+<success_criteria>
+- [ ] Context loaded (Tier 1 all files, Tier 2 ICP/CHANNELS/METRICS/CALENDAR, full POSITIONING.md)
+- [ ] Campaign validated and phase order checked (D-08)
+- [ ] Outcome metric enforced -- valid business outcome with target value and measurement window (D-06, LIFE-04)
+- [ ] Output metric collected or flagged as missing (D-06)
+- [ ] All mandatory brief fields present in generated BRIEF.md (D-07)
+- [ ] Positioning check gate executed with all 5 checks from brief-positioning-check.md (D-05, LIFE-05)
+- [ ] BRIEF.md written unconditionally -- never blocked by positioning drift (D-05)
+- [ ] Campaign state updated: phase=briefed, gate.outcome_metric, gate.positioning_check
+- [ ] OUTPUT_METRIC_MISSING flag visible in BRIEF.md when applicable
+</success_criteria>
+
+<output>
+- `.marketing/CAMPAIGNS/<slug>/BRIEF.md` (populated with all mandatory fields)
+</output>