taketomarket 2.2.0 → 2.3.1

package/workflows/discipline/affiliate-kit.md

@@ -1,3 +1,32 @@
+## Step 0: First-run inline education
+
+Read `.taketomarket/CONFIG.md`. Parse `first_run_seen` (object) and `inline_education` (boolean, default true).
+
+If `inline_education` is false: skip this step. Else if `first_run_seen.ttm-affiliate-kit` is not `true`, print the explainer below verbatim, then mark this skill as seen:
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" first-run mark ttm-affiliate-kit
+```
+
+Use this exact check (bash) to decide whether to print: `node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" first-run check ttm-affiliate-kit --raw` -- the JSON `seen` field is `true` once the explainer has run before.
+
+### Explainer for `/ttm-affiliate-kit`
+
+`/ttm-affiliate-kit` generates a complete affiliate / partner enablement
+package: positioned creative, copy variants per channel, claim cards
+with substantiation, and a one-pager partners can drop into their
+own funnels. Everything inherits your positioning invariant.
+
+Why it matters: affiliates and partners are the highest-drift channel
+because the assets leave your control. A structured kit with explicit
+positioning rails is the difference between affiliate-driven growth
+that compounds and affiliate-driven content that contradicts your
+own site within a quarter.
+
+(Canonical source: `references/inline-education-blurbs.md`. Embedded verbatim because workflows do not @-resolve files at runtime.)
+
+---
+
 <purpose>
 Generate a creative kit for affiliate partners including approved messaging, banner specs,
 email swipes, and tracking requirements. Uses affiliate playbook constraints for quality.
@@ -12,7 +41,7 @@ Single-pass analysis workflow per D-07.
 <constraints>
 ## POSITIONING.md is READ-ONLY
 
-**Do NOT modify `.marketing/POSITIONING.md` during this workflow.**
+**Do NOT modify `.taketomarket/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
@@ -43,11 +72,11 @@ If `AskUserQuestion` tool is not available in the current runtime, set `TEXT_MOD
 takeToMarket > LOADING CONTEXT FOR AFFILIATE KIT
 ```
 
-**Tier 1 summaries** (lines 1 to `<!-- END_SUMMARY -->`) from all 9 `.marketing/` reference files.
-**Tier 2 (full):** `.marketing/POSITIONING.md`, `.marketing/BRAND.md`, `.marketing/ICP.md`, `.marketing/METRICS.md`
+**Tier 1 summaries** (lines 1 to `<!-- END_SUMMARY -->`) from all 9 `.taketomarket/` reference files.
+**Tier 2 (full):** `.taketomarket/POSITIONING.md`, `.taketomarket/BRAND.md`, `.taketomarket/ICP.md`, `.taketomarket/METRICS.md`
 **Playbook gates:** @${CLAUDE_PLUGIN_ROOT}/playbooks/affiliate.md
 
-If `.marketing/POSITIONING.md` does not exist: Error and exit.
+If `.taketomarket/POSITIONING.md` does not exist: Error and exit.
 
 ---
 
@@ -106,7 +135,7 @@ Produce a complete kit with these sections:
 ## Step 4: Write Kit File
 
 Generate a URL-safe slug from `PRODUCT_NAME`.
-Write to `.marketing/AFFILIATE-KIT-[product-slug].md`.
+Write to `.taketomarket/AFFILIATE-KIT-[product-slug].md`.
 
 Kit file structure:
 ```markdown
@@ -139,9 +168,39 @@ Cookie Window: [duration]
 ========================================
 takeToMarket > AFFILIATE KIT COMPLETE
 ========================================
-Product: ${PRODUCT_NAME} | Sections: 5 | File: .marketing/AFFILIATE-KIT-[slug].md
+Product: ${PRODUCT_NAME} | Sections: 5 | File: .taketomarket/AFFILIATE-KIT-[slug].md
 ```
 
 Display summary of kit contents and confirm file location.
 
+---
+
+## Step 6: Final humanization (MANDATORY)
+
+Every external kit asset (partner email templates, kit copy, promotional snippets, etc.) MUST pass through `/ttm-humanize` before write.
+
+For each draft asset produced in this phase:
+1. Invoke `/ttm-humanize <draft-path>` via the Skill tool.
+2. Wait for the rewritten version.
+3. Write the humanized output to the final asset destination.
+4. Do not write the un-humanized draft.
+
+Internal state files (campaign briefs, manifests, STATE.md) are exempt.
+
 </process>
+
+<success_criteria>
+- [ ] All 5 sections generated (Approved Messaging, Email Swipes, Banner Specs, Tracking Requirements, Compliance Rules)
+- [ ] Approved claims and banned-language lists sourced from BRAND.md + POSITIONING.md
+- [ ] FTC disclosure included in every email swipe template
+- [ ] UTM format and attribution model present in tracking section
+- [ ] Kit file written to .taketomarket/AFFILIATE-KIT-[product-slug].md
+- [ ] Each external kit asset (partner emails, kit copy, snippets) passed through /ttm-humanize before write.
+</success_criteria>
+
+## What if this doesn't fit?
+
+Looks like /ttm-affiliate-kit can't do that yet.
+
+- Want a new skill? /ttm-request-skill
+- Existing skill needs work? /ttm-improve-skill

package/workflows/discipline/{email-preflight.md → email-check.md}

@@ -1,3 +1,31 @@
+## Step 0: First-run inline education
+
+Read `.taketomarket/CONFIG.md`. Parse `first_run_seen` (object) and `inline_education` (boolean, default true).
+
+If `inline_education` is false: skip this step. Else if `first_run_seen.ttm-email-check` is not `true`, print the explainer below verbatim, then mark this skill as seen:
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" first-run mark ttm-email-check
+```
+
+Use this exact check (bash) to decide whether to print: `node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" first-run check ttm-email-check --raw` -- the JSON `seen` field is `true` once the explainer has run before.
+
+### Explainer for `/ttm-email-check`
+
+`/ttm-email-check` is the email pre-flight. It runs a draft email
+through deliverability checks (spam-trigger phrases, structural red
+flags, list-hygiene reminders) and the positioning gate, plus a
+voice check against your BRAND.md. Output is a pass/fix-list.
+
+Why it matters: email is unforgiving -- one drift-laden send to a
+warm list can damage open rates for weeks. Treat this skill like a
+pre-commit hook for outbound: cheap, fast, and the only thing
+standing between your draft and your domain reputation.
+
+(Canonical source: `references/inline-education-blurbs.md`. Embedded verbatim because workflows do not @-resolve files at runtime.)
+
+---
+
 <purpose>
 Pre-send deliverability, dark-mode compatibility, and spam-trigger scan for email content.
 Evaluates against email playbook gate definitions and generates a go/no-go recommendation.
@@ -12,7 +40,7 @@ Single-pass analysis workflow per D-07.
 <constraints>
 ## POSITIONING.md is READ-ONLY
 
-**Do NOT modify `.marketing/POSITIONING.md` during this workflow.**
+**Do NOT modify `.taketomarket/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
@@ -43,11 +71,11 @@ If `AskUserQuestion` tool is not available in the current runtime, set `TEXT_MOD
 takeToMarket > LOADING CONTEXT FOR EMAIL PREFLIGHT
 ```
 
-**Tier 1 summaries** (lines 1 to `<!-- END_SUMMARY -->`) from all 9 `.marketing/` reference files.
-**Tier 2 (full):** `.marketing/BRAND.md` (voice/banned words check).
+**Tier 1 summaries** (lines 1 to `<!-- END_SUMMARY -->`) from all 9 `.taketomarket/` reference files.
+**Tier 2 (full):** `.taketomarket/BRAND.md` (voice/banned words check).
 **Playbook gates:** @${CLAUDE_PLUGIN_ROOT}/playbooks/email.md
 
-If `.marketing/POSITIONING.md` does not exist: Error and exit.
+If `.taketomarket/POSITIONING.md` does not exist: Error and exit.
 
 ---
 
@@ -148,3 +176,10 @@ VERDICT: [GO / CAUTION / NO-GO]
 ```
 
 </process>
+
+## What if this doesn't fit?
+
+Looks like /ttm-email-check can't do that yet.
+
+- Want a new skill? /ttm-request-skill
+- Existing skill needs work? /ttm-improve-skill

package/workflows/discipline/repurpose.md

@@ -1,3 +1,32 @@
+## Step 0: First-run inline education
+
+Read `.taketomarket/CONFIG.md`. Parse `first_run_seen` (object) and `inline_education` (boolean, default true).
+
+If `inline_education` is false: skip this step. Else if `first_run_seen.ttm-repurpose` is not `true`, print the explainer below verbatim, then mark this skill as seen:
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" first-run mark ttm-repurpose
+```
+
+Use this exact check (bash) to decide whether to print: `node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" first-run check ttm-repurpose --raw` -- the JSON `seen` field is `true` once the explainer has run before.
+
+### Explainer for `/ttm-repurpose`
+
+`/ttm-repurpose` takes a shipped hero asset and generates derivative
+assets for other channels (LinkedIn from a blog, email from a landing
+page, threads from a podcast transcript) while preserving the
+positioning invariant. Each derivative runs the full gate wall.
+
+Why it matters: most marketing teams produce one-off assets; the
+compound advantage comes from making one hero work across five
+channels. Repurpose is the systematic version of that, with explicit
+provenance so you can trace any channel asset back to the parent and
+the brief.
+
+(Canonical source: `references/inline-education-blurbs.md`. Embedded verbatim because workflows do not @-resolve files at runtime.)
+
+---
+
 <purpose>
 Fan out a long-form source asset into derivative assets across channels. Executes full
 brief-produce-verify per derivative with hero-first Task() orchestration. Each derivative
@@ -14,7 +43,7 @@ This is NOT a lightweight command -- it runs the full production lifecycle per d
 <constraints>
 ## POSITIONING.md is READ-ONLY
 
-**Do NOT modify `.marketing/POSITIONING.md` during this workflow.**
+**Do NOT modify `.taketomarket/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
@@ -68,21 +97,21 @@ SOURCE_ASSET_PATH=$(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`
+- `.taketomarket/POSITIONING.md`
+- `.taketomarket/BRAND.md`
+- `.taketomarket/ICP.md`
+- `.taketomarket/CHANNELS.md`
+- `.taketomarket/STATE.md` (frontmatter only)
+- `.taketomarket/CALENDAR.md`
+- `.taketomarket/COMPETITORS.md`
+- `.taketomarket/METRICS.md`
+- `.taketomarket/LEARNINGS.md`
 
 Read Tier 2 (full content) for production context:
-- `.marketing/POSITIONING.md`
-- `.marketing/CHANNELS.md`
-- `.marketing/BRAND.md`
-- `.marketing/ICP.md`
+- `.taketomarket/POSITIONING.md`
+- `.taketomarket/CHANNELS.md`
+- `.taketomarket/BRAND.md`
+- `.taketomarket/ICP.md`
 
 ---
 
@@ -95,8 +124,8 @@ Parse SOURCE_ASSET_PATH from $ARGUMENTS.
 Use path.resolve() equivalent to canonicalize the path, then verify:
 
 1. **File exists** at the specified path
-2. **Path is within `.marketing/CAMPAIGNS/`** directory -- reject any path that does not
-   resolve to a location under `.marketing/CAMPAIGNS/[slug]/ASSETS/`
+2. **Path is within `.taketomarket/CAMPAIGNS/`** directory -- reject any path that does not
+   resolve to a location under `.taketomarket/CAMPAIGNS/[slug]/ASSETS/`
 3. **Campaign is in appropriate phase** -- read the campaign's STATE.md and confirm phase
    is one of: produced, verified, reviewed, fixed, or shipped
 
@@ -109,7 +138,7 @@ Extract from the validated path and campaign data:
 
 If validation fails at any step, display a specific error:
 - Path not found: "Source asset not found at [path]. Check the file path and try again."
-- Not in CAMPAIGNS: "Source asset must be within a .marketing/CAMPAIGNS/[slug]/ASSETS/ directory."
+- Not in CAMPAIGNS: "Source asset must be within a .taketomarket/CAMPAIGNS/[slug]/ASSETS/ directory."
 - Wrong phase: "Campaign [slug] is in phase [phase]. Repurpose requires produced, verified, reviewed, fixed, or shipped."
 - Not in MANIFEST: "Source asset not found in MANIFEST.json. Was this asset produced by /ttm-produce?"
 
@@ -117,7 +146,7 @@ If validation fails at any step, display a specific error:
 
 ## Step 3: Select Target Channels
 
-Read `.marketing/CHANNELS.md` active channels list.
+Read `.taketomarket/CHANNELS.md` active channels list.
 
 Parse all active channels from CHANNELS.md. Remove SOURCE_CHANNEL from the list
 (do not repurpose to the same channel the source was produced for).
@@ -166,12 +195,12 @@ takeToMarket > GENERATING DERIVATIVE BRIEFS ([N] channels)
 For each target channel, generate a channel-adapted derivative brief (per D-11).
 
 Read the source asset content and extract the core message/thesis.
-Cross-reference `.marketing/CHANNELS.md` for each target channel's configuration:
+Cross-reference `.taketomarket/CHANNELS.md` for each target channel's configuration:
 - Format requirements (content type, structure)
 - Typical length/word count for the channel
 - Audience overlap with source channel
 
-Cross-reference `.marketing/BRAND.md` for tone-per-context adjustments if defined
+Cross-reference `.taketomarket/BRAND.md` for tone-per-context adjustments if defined
 for the target channel.
 
 Write each brief with these sections:
@@ -182,7 +211,7 @@ Write each brief with these sections:
 - **Positioning Anchor:** Primary differentiator and proof points from POSITIONING.md (direct quote)
 - **Outcome Metric:** Inherit from campaign BRIEF.md, or channel-default from CHANNELS.md baselines
 
-Write each brief to: `.marketing/CAMPAIGNS/${CAMPAIGN_SLUG}/REPURPOSE-BRIEF-${CHANNEL_SLUG}.md`
+Write each brief to: `.taketomarket/CAMPAIGNS/${CAMPAIGN_SLUG}/REPURPOSE-BRIEF-${CHANNEL_SLUG}.md`
 
 ---
 
@@ -195,12 +224,12 @@ takeToMarket > REPURPOSING: HERO DERIVATIVE ([HERO_CHANNEL])
 Read the agent prompt template from `${CLAUDE_PLUGIN_ROOT}/agents/ttm-producer.md`.
 
 Fill placeholders:
-- `[BRIEF_PATH]` --> `.marketing/CAMPAIGNS/${CAMPAIGN_SLUG}/REPURPOSE-BRIEF-${HERO_CHANNEL_SLUG}.md`
-- `[POSITIONING_PATH]` --> `.marketing/POSITIONING.md`
-- `[BRAND_PATH]` --> `.marketing/BRAND.md`
-- `[ICP_PATH]` --> `.marketing/ICP.md`
+- `[BRIEF_PATH]` --> `.taketomarket/CAMPAIGNS/${CAMPAIGN_SLUG}/REPURPOSE-BRIEF-${HERO_CHANNEL_SLUG}.md`
+- `[POSITIONING_PATH]` --> `.taketomarket/POSITIONING.md`
+- `[BRAND_PATH]` --> `.taketomarket/BRAND.md`
+- `[ICP_PATH]` --> `.taketomarket/ICP.md`
 - `[PLAYBOOK_PATH]` --> resolved playbook for HERO_CHANNEL (from `${CLAUDE_PLUGIN_ROOT}/playbooks/${CHANNEL_TYPE}.md`), or `"none"` if not found
-- `[OUTPUT_PATH]` --> `.marketing/CAMPAIGNS/${CAMPAIGN_SLUG}/ASSETS/R-01-${HERO_CHANNEL_SLUG}.md`
+- `[OUTPUT_PATH]` --> `.taketomarket/CAMPAIGNS/${CAMPAIGN_SLUG}/ASSETS/R-01-${HERO_CHANNEL_SLUG}.md`
 - `[ASSET_TYPE]` --> derivative content type for this channel
 - `[CHANNEL]` --> HERO_CHANNEL name
 - `[HERO_PATH]` --> SOURCE_ASSET_PATH (the original source serves as the "hero" reference)
@@ -213,7 +242,7 @@ Call Task() with the populated prompt.
 
 After Task() returns, verify the hero derivative file exists and has content:
 ```bash
-test -s ".marketing/CAMPAIGNS/${CAMPAIGN_SLUG}/ASSETS/R-01-${HERO_CHANNEL_SLUG}.md"
+test -s ".taketomarket/CAMPAIGNS/${CAMPAIGN_SLUG}/ASSETS/R-01-${HERO_CHANNEL_SLUG}.md"
 ```
 
 If the file is empty or missing:
@@ -245,7 +274,7 @@ All derivative Task() calls run in parallel (per D-13 wave-parallel pattern).
 
 After ALL Task() calls complete, verify each output file exists and has content (> 50 chars):
 ```bash
-test -s ".marketing/CAMPAIGNS/${CAMPAIGN_SLUG}/ASSETS/R-${NN}-${CHANNEL_SLUG}.md"
+test -s ".taketomarket/CAMPAIGNS/${CAMPAIGN_SLUG}/ASSETS/R-${NN}-${CHANNEL_SLUG}.md"
 ```
 
 For any derivative that failed (file empty or missing):
@@ -309,6 +338,20 @@ Display a banner with:
 - Manifest and brief file paths
 - Next steps: `/ttm-verify`, `/ttm-review`, `/ttm-fix`
 
+---
+
+## Step 10: Final humanization (MANDATORY)
+
+Every audience-facing asset MUST pass through `/ttm-humanize` before write.
+
+For each draft asset produced in this phase:
+1. For each derivative produced (long-form -> short-form, email -> social, etc.), invoke `/ttm-humanize <derivative-path>` via the Skill tool.
+2. Wait for the rewritten version.
+3. Write the humanized output to the final asset destination.
+4. Do not write the un-humanized draft.
+
+Internal state files (campaign briefs, manifests, STATE.md) are exempt.
+
 </process>
 
 <success_criteria>
@@ -320,10 +363,18 @@ Display a banner with:
 - [ ] Simplified verification (positioning drift, format, voice) runs per derivative
 - [ ] All derivatives tracked in MANIFEST.json with source_asset_id
 - [ ] Completion banner with per-derivative verification results
+- [ ] Each derivative passed through /ttm-humanize before write.
 </success_criteria>
 
 <output>
-- `.marketing/CAMPAIGNS/${SLUG}/REPURPOSE-BRIEF-*.md` (per-channel derivative briefs)
-- `.marketing/CAMPAIGNS/${SLUG}/ASSETS/R-*.md` (produced derivative assets)
-- `.marketing/CAMPAIGNS/${SLUG}/MANIFEST.json` (updated with derivative entries)
+- `.taketomarket/CAMPAIGNS/${SLUG}/REPURPOSE-BRIEF-*.md` (per-channel derivative briefs)
+- `.taketomarket/CAMPAIGNS/${SLUG}/ASSETS/R-*.md` (produced derivative assets)
+- `.taketomarket/CAMPAIGNS/${SLUG}/MANIFEST.json` (updated with derivative entries)
 </output>
+
+## What if this doesn't fit?
+
+Looks like /ttm-repurpose can't do that yet.
+
+- Want a new skill? /ttm-request-skill
+- Existing skill needs work? /ttm-improve-skill

package/workflows/discipline/{aeo-check.md → seo/aeo.md}

@@ -13,7 +13,7 @@ Single-pass analysis workflow per D-07.
 <constraints>
 ## POSITIONING.md is READ-ONLY
 
-**Do NOT modify `.marketing/POSITIONING.md` during this workflow.**
+**Do NOT modify `.taketomarket/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
@@ -44,11 +44,11 @@ If `AskUserQuestion` tool is not available in the current runtime, set `TEXT_MOD
 takeToMarket > LOADING CONTEXT FOR AEO CHECK
 ```
 
-**Tier 1 summaries** (lines 1 to `<!-- END_SUMMARY -->`) from all 9 `.marketing/` reference files.
-**Tier 2 (full):** `.marketing/POSITIONING.md` (differentiator alignment check).
+**Tier 1 summaries** (lines 1 to `<!-- END_SUMMARY -->`) from all 9 `.taketomarket/` reference files.
+**Tier 2 (full):** `.taketomarket/POSITIONING.md` (differentiator alignment check).
 **Playbook gates:** @${CLAUDE_PLUGIN_ROOT}/playbooks/aeo.md
 
-If `.marketing/POSITIONING.md` does not exist: Error and exit.
+If `.taketomarket/POSITIONING.md` does not exist: Error and exit.
 
 ---
 
@@ -174,7 +174,14 @@ takeToMarket > AEO CHECK COMPLETE
 Query: ${TARGET_QUERY} | Citability Score: [score]%
 ```
 
-Offer: "Save this report to .marketing/AUDITS/aeo-check-[date].md? (yes/no)"
-If yes: create `.marketing/AUDITS/` directory if needed and write the report.
+Offer: "Save this report to .taketomarket/AUDITS/aeo-check-[date].md? (yes/no)"
+If yes: create `.taketomarket/AUDITS/` directory if needed and write the report.
 
 </process>
+
+## What if this doesn't fit?
+
+Looks like /ttm-seo can't do that yet.
+
+- Want a new skill? /ttm-request-skill
+- Existing skill needs work? /ttm-improve-skill

package/workflows/discipline/{seo-audit.md → seo/audit.md}

@@ -12,7 +12,7 @@ Single-pass analysis workflow per D-07.
 <constraints>
 ## POSITIONING.md is READ-ONLY
 
-**Do NOT modify `.marketing/POSITIONING.md` during this workflow.**
+**Do NOT modify `.taketomarket/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
@@ -43,11 +43,11 @@ If `AskUserQuestion` tool is not available in the current runtime, set `TEXT_MOD
 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).
+**Tier 1 summaries** (lines 1 to `<!-- END_SUMMARY -->`) from all 9 `.taketomarket/` reference files.
+**Tier 2 (full):** `.taketomarket/CHANNELS.md` (channel-specific SEO config).
 **Playbook gates:** @${CLAUDE_PLUGIN_ROOT}/playbooks/seo.md
 
-If `.marketing/POSITIONING.md` does not exist: Error and exit.
+If `.taketomarket/POSITIONING.md` does not exist: Error and exit.
 
 ---
 
@@ -163,7 +163,14 @@ 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.
+Offer: "Save this report to .taketomarket/AUDITS/seo-audit-[date].md? (yes/no)"
+If yes: create `.taketomarket/AUDITS/` directory if needed and write the report.
 
 </process>
+
+## What if this doesn't fit?
+
+Looks like /ttm-seo can't do that yet.
+
+- Want a new skill? /ttm-request-skill
+- Existing skill needs work? /ttm-improve-skill

package/workflows/discipline/{keyword-map.md → seo/keyword-map.md}

@@ -13,7 +13,7 @@ Single-pass analysis workflow per D-07.
 <constraints>
 ## POSITIONING.md is READ-ONLY
 
-**Do NOT modify `.marketing/POSITIONING.md` during this workflow.**
+**Do NOT modify `.taketomarket/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
@@ -44,10 +44,10 @@ If `AskUserQuestion` tool is not available in the current runtime, set `TEXT_MOD
 takeToMarket > LOADING CONTEXT FOR KEYWORD MAP
 ```
 
-**Tier 1 summaries** (lines 1 to `<!-- END_SUMMARY -->`) from all 9 `.marketing/` reference files.
-**Tier 2 (full):** `.marketing/POSITIONING.md`, `.marketing/CHANNELS.md`, `.marketing/COMPETITORS.md`
+**Tier 1 summaries** (lines 1 to `<!-- END_SUMMARY -->`) from all 9 `.taketomarket/` reference files.
+**Tier 2 (full):** `.taketomarket/POSITIONING.md`, `.taketomarket/CHANNELS.md`, `.taketomarket/COMPETITORS.md`
 
-If `.marketing/POSITIONING.md` does not exist: Error and exit.
+If `.taketomarket/POSITIONING.md` does not exist: Error and exit.
 
 ---
 
@@ -85,7 +85,7 @@ Group into topic clusters with pillar-cluster relationships.
 
 ## Step 4: Output Keyword Map
 
-Write to `.marketing/KEYWORD-MAP.md`:
+Write to `.taketomarket/KEYWORD-MAP.md`:
 
 ```markdown
 # Keyword Map
@@ -117,9 +117,16 @@ Keywords competitors rank for that are not covered:
 ========================================
 takeToMarket > KEYWORD MAP COMPLETE
 ========================================
-Clusters: [N] | Keywords: [total] | File: .marketing/KEYWORD-MAP.md
+Clusters: [N] | Keywords: [total] | File: .taketomarket/KEYWORD-MAP.md
 ```
 
 Display a summary table of clusters with keyword counts per cluster.
 
 </process>
+
+## What if this doesn't fit?
+
+Looks like /ttm-seo can't do that yet.
+
+- Want a new skill? /ttm-request-skill
+- Existing skill needs work? /ttm-improve-skill

package/workflows/education/ttm-101.md

@@ -0,0 +1,114 @@
+# /ttm-101 Workflow
+
+Print engineer-friendly explanations of core marketing concepts.
+
+## Section 1: Positioning
+
+**Engineering analogy:** Positioning is your API contract. It's the promise of what your product is, who it's for, and what it does that competitors don't. Every downstream marketing asset MUST adhere to it.
+
+Without positioning:
+- Your homepage says one thing; your sales emails say another. Customers churn.
+- You build features for the wrong customer. Roadmap drift.
+- AI engines can't summarize who you are. You don't get cited.
+
+A positioning statement has 5 parts:
+1. **Category** — what kind of thing you are. ("Marketing OS for engineers")
+2. **Target audience** — who specifically. ("Developerneurs and solopreneurs with no marketing experience")
+3. **Primary differentiator** — the ONE thing competitors don't do. ("Positioning-invariant quality gates")
+4. **Proof points** — specific numbers/cases that back the differentiator.
+5. **Must-not-say** — terms you ban. (Why: prevents drift.)
+
+In takeToMarket, `.taketomarket/POSITIONING.md` holds this. The quality gate wall enforces it.
+
+## Section 2: ICP (Ideal Customer Profile)
+
+**Engineering analogy:** ICP is your user persona but enforced as a constraint. Anyone outside the ICP is anti-ICP — explicitly NOT a target.
+
+Without ICP discipline:
+- You market to everyone. Your message is bland. Nobody pays attention.
+- You build features for tire-kickers. Real customers churn.
+
+A good ICP has:
+- **Demographics:** role, company size, industry, geography.
+- **Psychographics:** what they believe, what they read, what they're frustrated by.
+- **JTBD:** the job they hire your product to do.
+- **Pain severity + frequency.**
+- **Anti-ICP:** who you explicitly avoid.
+
+In takeToMarket: `.taketomarket/ICP.md`.
+
+## Section 3: Channels
+
+**Engineering analogy:** Channels are deployment targets. Each has its own runtime + idioms. You don't deploy a React app to AWS Lambda raw — you containerize it. Same with marketing: you don't post a long-form essay on Twitter, you adapt it.
+
+Channels in takeToMarket:
+- **Organic Search / SEO** — content that ranks on Google.
+- **AEO (AI Engine Optimization)** — content that AI engines cite.
+- **LinkedIn** — professional social.
+- **Email** — direct + permissioned.
+- **Paid Ads** — Google Ads, Meta Ads, LinkedIn Ads.
+- **YouTube** — video content.
+- **Social** — Twitter/X, Instagram, TikTok.
+- **Events** — conferences, webinars.
+- **PR / Media** — press, podcast tours.
+- **Affiliate / Partnerships** — distribution via others.
+
+Each channel has a playbook (`playbooks/<channel>.md`) rewritten under THE industry leader for that channel.
+
+## Section 4: Funnel
+
+**Engineering analogy:** TOFU/MOFU/BOFU is a state machine. Users move through states. Each state has different content needs.
+
+- **TOFU (Top of Funnel):** Stranger. Doesn't know they have your problem. Content: blog posts, social posts, YouTube videos. Goal: awareness.
+- **MOFU (Middle of Funnel):** Aware of problem, evaluating solutions. Content: comparison pages, use-case pages, free tools, lead magnets. Goal: evaluation.
+- **BOFU (Bottom of Funnel):** Ready to buy. Content: pricing pages, demos, case studies, testimonials. Goal: conversion.
+
+In takeToMarket: each asset is tagged with its funnel position in the campaign brief.
+
+## Section 5: AEO vs SEO
+
+**Engineering analogy:** SEO is for search engines (Google). AEO is for AI engines (ChatGPT, Claude, Perplexity, Gemini). They optimize for different consumers.
+
+- **SEO signals:** keywords, backlinks, page speed, mobile-friendliness, internal linking, schema markup.
+- **AEO signals:** citability (clear answer blocks), structured data, definitional sentences, llms.txt, recent updates.
+
+Modern marketing optimizes for BOTH. takeToMarket builds AEO-first while maintaining SEO floor.
+
+## Section 6: The 9-phase lifecycle
+
+**Engineering analogy:** Every campaign goes through a state machine with 9 states. Each state has entry + exit conditions. Quality gates between states catch defects early (cheaper than catching them in production).
+
+1. **Brief** — define outcome metric + positioning anchor + channel mix.
+2. **Discover** — research market, audience, competitors.
+3. **Produce** — generate assets in fresh contexts loaded with brief + refs.
+4. **Verify** — run quality gates on every asset.
+5. **Review** — present to user for approval.
+6. **Ship** — publish/deploy.
+7. **Measure** — analyze analytics against outcome metric.
+8. **Learn** — extract lessons, update reference files.
+9. **Fix** — root-cause + rework failed assets (capped at 3 attempts).
+
+## Section 7: takeToMarket invariants
+
+**Engineering analogy:** These are unit-test-enforced contracts. Every asset must satisfy them or it doesn't ship.
+
+1. **Verifiable outcome metric.** Every campaign declares ONE metric upfront. No metric → no campaign.
+2. **Positioning-invariant quality gate wall.** Every asset is checked against POSITIONING.md before ship. Drift = block.
+3. **Mandatory humanizer pass.** Every audience-facing asset passes through `/ttm-humanize` as the final step.
+4. **Compound learnings.** Every campaign's lessons update `.taketomarket/LEARNINGS.md`. Future campaigns inherit.
+
+---
+
+## End-of-tour
+
+Pick one to do now:
+- `/ttm-init` — set up your workspace if you haven't.
+- `/ttm-new-campaign` — start a campaign.
+- `/ttm-101 --section <name>` — re-read any section.
+
+## What if this doesn't fit?
+
+Looks like /ttm-101 can't do that yet.
+
+- Want a new skill? /ttm-request-skill
+- Existing skill needs work? /ttm-improve-skill

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

@@ -80,7 +80,7 @@ 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.
+Review .taketomarket/POSITIONING.md and adjust the brief if needed.
 Run /ttm-positioning-check for a full audit.
 -->
 ```