taketomarket 0.1.0

package/workflows/lifecycle/produce.md

@@ -0,0 +1,383 @@
+<purpose>
+Production orchestration workflow for /ttm-produce. Generates content assets in
+fresh Task() subagent contexts loaded with brief + positioning (full) + brand (full) +
+ICP (full) + playbook (per D-03). Hero asset produced first (blocking), then
+derivatives spawned in parallel (per D-01). Writes MANIFEST.json for verify
+consumption (per D-11).
+</purpose>
+
+<required_reading>
+@${CLAUDE_PLUGIN_ROOT}/references/context-loading.md
+@${CLAUDE_PLUGIN_ROOT}/agents/ttm-producer.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:
+```
+
+---
+
+## 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 production context (per D-03):
+- `.marketing/POSITIONING.md`
+- `.marketing/BRAND.md`
+- `.marketing/ICP.md`
+
+Read campaign-specific files (always full-load per context-loading.md rule 4):
+- `.marketing/CAMPAIGNS/${SLUG}/STATE.md`
+- `.marketing/CAMPAIGNS/${SLUG}/BRIEF.md`
+
+---
+
+## Step 2: Validate Campaign State
+
+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 `"briefed"`: This is the expected state. Proceed normally.
+
+- If phase is `"created"` or `"researched"`:
+  Warn the user:
+  "Campaign has not been briefed yet. Run `/ttm-brief ${SLUG}` first to generate a brief before producing content."
+  Exit.
+
+- If phase is `"produced"` or later (verified, reviewed, fixed, shipped, measured, learned):
+  Warn the user:
+  "Campaign is already in phase '${PHASE}'. Re-producing will overwrite existing assets in CAMPAIGNS/${SLUG}/ASSETS/. Proceed?"
+  Wait for user confirmation. If user declines, exit.
+
+---
+
+## Step 3: Parse Assets List from Brief
+
+```
+takeToMarket > PARSING BRIEF
+```
+
+Read `.marketing/CAMPAIGNS/${SLUG}/BRIEF.md`.
+
+Extract the assets list from the brief. The brief contains an "Assets List" section (created by /ttm-brief) structured as a Markdown table with columns: asset type, channel, and role.
+
+Parse each row into an asset entry:
+- `type`: The asset type (e.g., blog-post, linkedin-post, email, landing-page)
+- `channel`: The target channel (e.g., organic-search, linkedin, email)
+- `is_hero`: `true` for the FIRST asset in the list, `false` for all others (per D-01)
+
+The FIRST asset in the list is the hero asset. All others are derivatives.
+
+If no assets list is found in the brief, or if the table is empty:
+  Error: "Brief has no assets list -- run `/ttm-brief ${SLUG}` first to generate a complete brief."
+  Exit.
+
+Store the parsed list as `ASSETS_LIST` with the total count as `TOTAL_ASSETS`.
+
+---
+
+## Step 4: Resolve Playbooks
+
+For each asset in `ASSETS_LIST`:
+
+1. Map the asset type to a discipline playbook using the PLAYBOOK_MAP lookup table:
+
+   **PLAYBOOK_MAP** (asset type slug -> playbook filename):
+
+   | Asset Type | Playbook File | Discipline |
+   |------------|--------------|------------|
+   | blog-post | seo.md | SEO |
+   | landing-page | seo.md | SEO |
+   | pillar-page | seo.md | SEO |
+   | programmatic-seo | seo.md | SEO |
+   | faq-page | aeo.md | AEO |
+   | knowledge-base | aeo.md | AEO |
+   | how-to-guide | aeo.md | AEO |
+   | email | email.md | Email |
+   | email-sequence | email.md | Email |
+   | newsletter | email.md | Email |
+   | linkedin-post | linkedin.md | LinkedIn |
+   | linkedin-article | linkedin.md | LinkedIn |
+   | linkedin-carousel | linkedin.md | LinkedIn |
+   | social-post | social.md | Social |
+   | twitter-thread | social.md | Social |
+   | instagram-carousel | social.md | Social |
+   | youtube-video | youtube.md | YouTube |
+   | youtube-short | youtube.md | YouTube |
+   | paid-ad | paid-ads.md | Paid Ads |
+   | google-ad | paid-ads.md | Paid Ads |
+   | meta-ad | paid-ads.md | Paid Ads |
+   | affiliate-kit | affiliate.md | Affiliate |
+   | affiliate-creative | affiliate.md | Affiliate |
+   | press-release | pr-media.md | PR/Media |
+   | media-pitch | pr-media.md | PR/Media |
+   | event-landing | events.md | Events |
+   | webinar-funnel | events.md | Events |
+   | event-recap | events.md | Events |
+
+   For the given asset type:
+   - Look up the asset type in PLAYBOOK_MAP
+   - If found: set `PLAYBOOK_FILE` to the mapped filename
+   - If NOT found: set `PLAYBOOK_FILE` to the asset type slug with `.md` extension (fallback: `${TYPE}.md`)
+
+2. Resolve the playbook file path: `${CLAUDE_PLUGIN_ROOT}/playbooks/${PLAYBOOK_FILE}`
+
+3. Check if the playbook file exists:
+   ```bash
+   test -f "${CLAUDE_PLUGIN_ROOT}/playbooks/${PLAYBOOK_FILE}"
+   ```
+
+4. If playbook exists: Record the full path as the asset's `playbook_path`.
+
+5. If playbook does NOT exist: Log a warning:
+   ```
+   takeToMarket > WARNING: No playbook found for "${TYPE}" (tried ${PLAYBOOK_FILE}) -- producing with base context only
+   ```
+   Set the asset's `playbook_path` to `"none"`.
+
+This is the loading MECHANISM only -- playbook content files are created in Phase 8.
+
+---
+
+## Step 5: Produce Hero Asset
+
+```
+takeToMarket > PRODUCING HERO ASSET
+```
+
+Identify the hero asset (first entry in `ASSETS_LIST`).
+
+Read the agent prompt template from `${CLAUDE_PLUGIN_ROOT}/agents/ttm-producer.md`.
+
+Fill all placeholders with actual paths:
+- `[BRIEF_PATH]` --> `.marketing/CAMPAIGNS/${SLUG}/BRIEF.md`
+- `[POSITIONING_PATH]` --> `.marketing/POSITIONING.md`
+- `[BRAND_PATH]` --> `.marketing/BRAND.md`
+- `[ICP_PATH]` --> `.marketing/ICP.md`
+- `[PLAYBOOK_PATH]` --> resolved playbook path from Step 4, or `"none"`
+- `[OUTPUT_PATH]` --> `.marketing/CAMPAIGNS/${SLUG}/ASSETS/01-${HERO_TYPE}-${HERO_CHANNEL}.md`
+- `[ASSET_TYPE]` --> hero asset type from brief (e.g., "blog-post")
+- `[CHANNEL]` --> hero asset channel from brief (e.g., "organic-search")
+- `[HERO_PATH]` --> `none` (this IS the hero asset)
+
+Call Task() with the populated prompt.
+
+**WAIT** for Task() to complete. The hero MUST finish before any derivatives are spawned.
+
+After Task() returns, verify the hero file exists and has content:
+```bash
+test -s ".marketing/CAMPAIGNS/${SLUG}/ASSETS/01-${HERO_TYPE}-${HERO_CHANNEL}.md"
+```
+
+If the file is empty or missing:
+  Error: "Hero asset production failed -- file not written by subagent. Check the brief for completeness and try again."
+  Exit.
+
+Store the hero filename as `HERO_FILE` for derivative reference.
+
+---
+
+## Step 6: Produce Derivative Assets
+
+If `TOTAL_ASSETS` is 1 (hero only), skip this step.
+
+```
+takeToMarket > PRODUCING DERIVATIVES (${N} assets)
+```
+Where N = TOTAL_ASSETS - 1.
+
+For each derivative asset in `ASSETS_LIST` (all entries after the hero):
+
+1. Read the agent prompt template from `${CLAUDE_PLUGIN_ROOT}/agents/ttm-producer.md`.
+
+2. Assign a sequential filename:
+   - Asset 2: `02-${TYPE}-${CHANNEL}.md`
+   - Asset 3: `03-${TYPE}-${CHANNEL}.md`
+   - etc.
+
+3. Fill all placeholders:
+   - `[BRIEF_PATH]` --> `.marketing/CAMPAIGNS/${SLUG}/BRIEF.md`
+   - `[POSITIONING_PATH]` --> `.marketing/POSITIONING.md`
+   - `[BRAND_PATH]` --> `.marketing/BRAND.md`
+   - `[ICP_PATH]` --> `.marketing/ICP.md`
+   - `[PLAYBOOK_PATH]` --> resolved playbook path from Step 4, or `"none"`
+   - `[OUTPUT_PATH]` --> `.marketing/CAMPAIGNS/${SLUG}/ASSETS/${NN}-${TYPE}-${CHANNEL}.md`
+   - `[ASSET_TYPE]` --> derivative asset type
+   - `[CHANNEL]` --> derivative asset channel
+   - `[HERO_PATH]` --> `.marketing/CAMPAIGNS/${SLUG}/ASSETS/${HERO_FILE}`
+
+4. Call Task() with the populated prompt.
+
+All derivative Task() calls can run in parallel (per D-01 wave-parallel pattern).
+
+After ALL derivative Task() calls complete, verify each derivative file exists and has content:
+```bash
+test -s ".marketing/CAMPAIGNS/${SLUG}/ASSETS/${NN}-${TYPE}-${CHANNEL}.md"
+```
+
+For any derivative that failed (file empty or missing):
+- Log a warning: `takeToMarket > WARNING: Derivative ${NN}-${TYPE}-${CHANNEL}.md failed -- file not written`
+- Continue with the remaining assets. Do NOT abort the entire production run.
+
+Track successful and failed derivatives for the manifest.
+
+---
+
+## Step 7: Write Production Manifest
+
+```
+takeToMarket > WRITING MANIFEST
+```
+
+Read the manifest template from `${CLAUDE_PLUGIN_ROOT}/templates/production-manifest.json`.
+
+Fill with actual values:
+
+```json
+{
+  "campaign": "${SLUG}",
+  "produced_at": "${ISO_TIMESTAMP}",
+  "context_loaded": {
+    "brief": ".marketing/CAMPAIGNS/${SLUG}/BRIEF.md",
+    "positioning": ".marketing/POSITIONING.md",
+    "brand": ".marketing/BRAND.md",
+    "icp": ".marketing/ICP.md"
+  },
+  "hero": {
+    "asset_id": 1,
+    "name": "01-${HERO_TYPE}-${HERO_CHANNEL}",
+    "type": "${HERO_TYPE}",
+    "channel": "${HERO_CHANNEL}",
+    "playbook": "${HERO_PLAYBOOK_PATH_OR_NONE}",
+    "file": "ASSETS/01-${HERO_TYPE}-${HERO_CHANNEL}.md"
+  },
+  "derivatives": [
+    {
+      "asset_id": 2,
+      "name": "02-${TYPE}-${CHANNEL}",
+      "type": "${TYPE}",
+      "channel": "${CHANNEL}",
+      "playbook": "${PLAYBOOK_PATH_OR_NONE}",
+      "file": "ASSETS/02-${TYPE}-${CHANNEL}.md",
+      "derived_from": 1
+    }
+  ],
+  "total_assets": ${TOTAL_SUCCESSFUL_ASSETS}
+}
+```
+
+Generate the timestamp:
+```bash
+TIMESTAMP=$(node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" timestamp --raw)
+```
+
+Only include successfully produced assets (those that passed the `test -s` check) in the manifest.
+If any derivatives failed, `total_assets` reflects only the successful count.
+
+Write the completed manifest to `.marketing/CAMPAIGNS/${SLUG}/MANIFEST.json`.
+
+The manifest is the ONLY bridge between produce and verify contexts (per D-11). Verify reads
+this file to discover which assets exist and what context was loaded during production.
+
+---
+
+## Step 8: Update Campaign State and Summary
+
+Update campaign phase:
+```bash
+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 produced
+node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" campaign update "${SLUG}" phase.produced "$TIMESTAMP"
+```
+
+Display completion banner:
+```
+takeToMarket > PRODUCTION COMPLETE
+
+Assets produced: ${TOTAL_SUCCESSFUL_ASSETS}
+Hero: 01-${HERO_TYPE}-${HERO_CHANNEL}.md
+Derivatives: [list of derivative filenames]
+Manifest: .marketing/CAMPAIGNS/${SLUG}/MANIFEST.json
+
+[If any derivatives failed:]
+WARNING: ${FAILED_COUNT} derivative(s) failed production. Check the manifest for details.
+
+Next: Run /ttm-verify ${SLUG} to validate assets against quality gates
+```
+
+</process>
+
+<success_criteria>
+- [ ] All assets from brief's assets list written to CAMPAIGNS/<slug>/ASSETS/
+- [ ] Hero asset produced before derivatives (sequential then parallel)
+- [ ] Each subagent loaded with brief + positioning (full) + brand (full) + ICP (full) + playbook
+- [ ] MANIFEST.json written with all successful asset entries
+- [ ] Campaign STATE.md updated to phase=produced with timestamp
+- [ ] No playbook errors (graceful fallback for missing playbooks with warning)
+- [ ] Failed derivatives logged but do not abort the run
+</success_criteria>
+
+<output>
+- `.marketing/CAMPAIGNS/${SLUG}/ASSETS/*.md` (produced content files)
+- `.marketing/CAMPAIGNS/${SLUG}/MANIFEST.json` (production manifest for /ttm-verify)
+</output>

package/workflows/lifecycle/research.md

@@ -0,0 +1,264 @@
+<purpose>
+Market and audience research workflow that generates a structured RESEARCH.md for a
+campaign. Detects WebSearch tool availability at runtime and falls back to manual paste
+when web search tools are unavailable. Every insight is tagged with a confidence level
+(HIGH/MEDIUM/LOW). Use after /ttm-new-campaign has created the campaign directory.
+</purpose>
+
+<required_reading>
+@${CLAUDE_PLUGIN_ROOT}/references/context-loading.md
+@${CLAUDE_PLUGIN_ROOT}/templates/campaign-research.md
+</required_reading>
+
+<process>
+
+## Step 1: Load Context
+
+```
+takeToMarket > LOADING CONTEXT
+```
+
+Read Tier 1 summary blocks (content between `<!-- _SUMMARY -->` and `<!-- END_SUMMARY -->`)
+from all 9 `.marketing/` reference files:
+
+- `.marketing/POSITIONING.md` (lines 1 to `<!-- END_SUMMARY -->`)
+- `.marketing/BRAND.md` (lines 1 to `<!-- END_SUMMARY -->`)
+- `.marketing/ICP.md` (lines 1 to `<!-- END_SUMMARY -->`)
+- `.marketing/CHANNELS.md` (lines 1 to `<!-- END_SUMMARY -->`)
+- `.marketing/STATE.md` (frontmatter only)
+- `.marketing/CALENDAR.md` (lines 1 to `<!-- END_SUMMARY -->`)
+- `.marketing/COMPETITORS.md` (lines 1 to `<!-- END_SUMMARY -->`)
+- `.marketing/METRICS.md` (lines 1 to `<!-- END_SUMMARY -->`)
+- `.marketing/LEARNINGS.md` (lines 1 to `<!-- END_SUMMARY -->`)
+
+Read Tier 2 (full content) for:
+- `.marketing/COMPETITORS.md` (per context-loading.md loading matrix -- research loads Tier 2 COMPETITORS.md)
+
+---
+
+## Step 2: Validate Campaign
+
+Extract the campaign slug from `$ARGUMENTS`. Strip any `--text` flag if present:
+```bash
+SLUG=$(echo "$ARGUMENTS" | sed 's/--text//g' | xargs)
+```
+
+If `$SLUG` is empty: ask the user "Which campaign should I research? Provide the campaign slug or name."
+
+Check the campaign exists:
+```bash
+ls ".marketing/CAMPAIGNS/${SLUG}/STATE.md" 2>/dev/null && echo "exists" || echo "missing"
+```
+
+**If "missing":**
+Tell the user: "Campaign `${SLUG}` does not exist. Run `/ttm-new-campaign ${SLUG}` first to create it."
+Exit -- do not continue.
+
+**If "exists":**
+Read campaign state:
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" campaign state "${SLUG}" --raw
+```
+
+Read the full campaign STATE.md (campaign files are always full-loaded per context-loading.md rule 4):
+- `.marketing/CAMPAIGNS/${SLUG}/STATE.md`
+
+Store the campaign name from the state for use in RESEARCH.md generation.
+
+---
+
+## Step 3: Phase Order Check
+
+Check the `phase` field from campaign state (Step 2).
+
+**If phase is NOT "created":**
+Warn the user: "Campaign `${SLUG}` is already in phase `${PHASE}`. Running research again will overwrite RESEARCH.md. Proceed anyway?"
+
+Wait for user confirmation before continuing.
+
+- If user confirms: continue to Step 4.
+- If user declines: exit with message "Research cancelled."
+
+**If phase is "created":**
+Continue to Step 4.
+
+---
+
+## Step 4: Understand Campaign
+
+Read the campaign name and any goal information from the campaign STATE.md.
+
+Ask the user (freeform, not AskUserQuestion):
+"What is the topic or focus of this campaign? What keywords or themes should I research?"
+
+Store the response as `RESEARCH_TOPIC`.
+
+---
+
+## Step 5: Tool Detection and Research
+
+Attempt a WebSearch call to detect tool availability. Use a minimal test query related
+to the campaign topic.
+
+### When WebSearch is available (SEARCH_MODE=web)
+
+```
+takeToMarket > RESEARCH MODE: WEB
+```
+
+- Use WebSearch for SERP queries based on `RESEARCH_TOPIC` and campaign keywords
+- Search for: market trends, competitor content, audience discussions, content gaps
+- Use WebFetch for competitor page content extraction when specific URLs are found
+- Cross-reference findings against `.marketing/COMPETITORS.md` (already loaded in Tier 2)
+- Tag insights with confidence levels:
+  - **HIGH**: verified source URL or cited data from web search results
+  - **MEDIUM**: indirect evidence or partial match from search results
+  - **LOW**: inference drawn from patterns without direct evidence
+
+### When WebSearch is NOT available (SEARCH_MODE=manual)
+
+```
+takeToMarket > RESEARCH MODE: MANUAL
+```
+
+Tell the user:
+```
+Web search tools are not available in this session.
+To get the best research, please paste any of the following:
+
+1. Google search results for:
+   - "[RESEARCH_TOPIC] [year]"
+   - "[RESEARCH_TOPIC] best practices"
+   - "[RESEARCH_TOPIC] vs [competitor terms]"
+2. Any competitor blog posts or landing pages you want analyzed
+3. Reddit/forum discussions about [RESEARCH_TOPIC]
+4. Any other market data you have (reports, articles, social posts)
+
+Paste your findings below and I will analyze them.
+```
+
+Wait for the user to paste content.
+
+Analyze pasted content against the loaded reference files (POSITIONING.md, ICP.md,
+COMPETITORS.md summaries). Extract structured insights from the pasted material.
+
+Tag all pasted insights as **MEDIUM** confidence (user-provided, not independently verified).
+Insights cross-referenced against known COMPETITORS.md data may be elevated to HIGH.
+
+### Hybrid mode
+
+If some insights come from web search and others from user paste, set method to "hybrid"
+and tag each insight according to its actual source.
+
+---
+
+## Step 6: Generate RESEARCH.md
+
+```
+takeToMarket > GENERATING RESEARCH
+```
+
+Read the template:
+```
+${CLAUDE_PLUGIN_ROOT}/templates/campaign-research.md
+```
+
+Fill all sections with research findings:
+
+- Replace `[CAMPAIGN_NAME]` with the campaign name from STATE.md
+- Replace `[SLUG]` with the campaign slug
+- Set **Researched:** to current timestamp:
+  ```bash
+  node ${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs timestamp --raw
+  ```
+- Set **Method:** to `web-search`, `manual-paste`, or `hybrid` based on Step 5
+
+### Section: Market Context
+Fill the insight table with market-level findings. Each row must have:
+- Insight text (specific, not generic)
+- Confidence tag: HIGH, MEDIUM, or LOW
+- Source (URL for web results, "user-provided" for paste, "inference" for AI analysis)
+
+### Section: Competitor Content Analysis
+Fill the competitor table from research findings cross-referenced with COMPETITORS.md:
+- Competitor name (from COMPETITORS.md or newly discovered)
+- Content type (blog, landing page, social, video, etc.)
+- Key message (their positioning or angle)
+- Gap/Opportunity (where our positioning can differentiate)
+
+### Section: Audience Insights
+Fill the insight table combining ICP.md Tier 1 summary with research findings:
+- What the target audience cares about
+- Pain points validated by research
+- Language patterns observed
+
+### Section: Ambient Narrative
+Write 2-3 paragraphs describing what the market already believes about this topic.
+What is the conventional wisdom? What assumptions do most buyers hold? Where does
+the market consensus create an opening for our positioning?
+
+### Section: Content Gaps
+Fill the gaps table with opportunities where quality content is missing or weak:
+- Gap description (specific topic or angle)
+- Opportunity size: HIGH (no quality content exists), MEDIUM (content exists but is weak), LOW (content exists but can be improved)
+- Difficulty: HIGH (requires deep expertise), MEDIUM (moderate effort), LOW (straightforward)
+
+### Section: Research Summary
+Write a 2-3 sentence summary that `/ttm-brief` will consume. Focus on: the biggest
+opportunity, the key audience insight, and the competitive angle.
+
+Write the completed research to:
+```
+.marketing/CAMPAIGNS/${SLUG}/RESEARCH.md
+```
+
+---
+
+## Step 7: Update Campaign State
+
+Update the campaign phase and timestamp:
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" campaign update "${SLUG}" phase researched
+```
+
+```bash
+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.researched "$TIMESTAMP"
+```
+
+Count the total insights generated across all sections.
+
+Display summary:
+```
+takeToMarket > RESEARCH COMPLETE
+
+Research saved to .marketing/CAMPAIGNS/${SLUG}/RESEARCH.md
+Method: [web-search|manual-paste|hybrid]
+Insights: [count] with confidence breakdown
+  HIGH: [count]
+  MEDIUM: [count]
+  LOW: [count]
+
+Next: Run /ttm-brief ${SLUG}
+```
+
+</process>
+
+<success_criteria>
+- [ ] Context loaded (Tier 1 all 9 files, Tier 2 COMPETITORS.md)
+- [ ] Campaign validated and slug extracted from $ARGUMENTS
+- [ ] Phase order checked (warn if not "created")
+- [ ] User provided research topic
+- [ ] Tool detection attempted before research (WebSearch probe)
+- [ ] Research generated with all 5 sections filled
+- [ ] Every insight tagged with confidence level (HIGH/MEDIUM/LOW)
+- [ ] RESEARCH.md written to campaign directory using template
+- [ ] Campaign state updated to phase=researched with timestamp
+</success_criteria>
+
+<output>
+- `.marketing/CAMPAIGNS/<slug>/RESEARCH.md` (populated with research)
+</output>