/auto

description: "Natural-language front door to the marketing pack (narrative/TALE, SEO/GEO/SITE, social/ECHO, email/SEND, Paid Ads/ROAS, influencer/STAR, launch/RAMP). Use when a marketing goal is open-ended or spans disciplines, when it is unclear which skill fits, or for requests like 'help with our marketing', 'grow our traffic', 'plan our launch', 'what should we post', 'is our messaging landing' — it infers the discipline and runs the smallest useful workflow. Add --deep for exhaustive, maximum-rigor, or stress-test runs."
argument-hint: "<natural-language-goal> [--deep]"

Auto Command

Run the marketing pack-local Aaron workflow (narrative/TALE + SEO/GEO/SITE + social/ECHO + email/SEND + Paid Ads/ROAS + influencer/STAR + launch/RAMP) implied by a natural-language goal, at the smallest safe depth — the natural-language front door to `/aaron-marketing:narrative`, `/aaron-marketing:seo-geo`, `/aaron-marketing:social`, `/aaron-marketing:email`, `/aaron-marketing:ad`, `/aaron-marketing:influencer`, and `/aaron-marketing:launch`. Add `--deep` for an exhaustive, phase-gated, maximum-rigor run.

Route

• resolver across all 120 skills (16 narrative + 16 SEO/GEO + 16 social + 16 email + 16 Paid Ads + 16 influencer + 16 launch + 8 protocol): brand narrative & messaging through `/aaron-marketing:narrative` (--phase trace|architect|land|evaluate), SEO/GEO through `/aaron-marketing:seo-geo` (--phase survey|implement|tune|evaluate), organic social through `/aaron-marketing:social` (--phase explore|craft|host|observe), email through `/aaron-marketing:email` (--phase setup|engage|nurture|deliver), Paid Ads through `/aaron-marketing:ad` (--phase research|orchestrate|activate|scale), influencer through `/aaron-marketing:influencer` (--phase scout|target|activate|report), launch through `/aaron-marketing:launch` (--phase research|assemble|mobilize|prove); or describe any goal here and it routes to the right skill

**Cross-discipline seams** — the word-sense splits the router owns (each discipline command's own **Scope edge** block holds the canonical intra-discipline hand-off detail; this list is the cross-discipline index):

• **"Launch" / "campaign" sense**: "launch a product **with creators**" → campaign-planner via `/aaron-marketing:influencer`; any other product launch (positioning, plan, launch day, Product Hunt / press / app-store, retro) → `/aaron-marketing:launch`; an email "launch campaign" (a broadcast) → `/aaron-marketing:email`; a paid "campaign launch" (turning ads on) → `/aaron-marketing:ad`.
• **"Post this" three-way split**: always-on calendar & net-new packages → social-calendar-builder / social-creative-builder via `/aaron-marketing:social`; "boost / repurpose this asset" → content-amplifier via `/aaron-marketing:influencer` (paid exec `/aaron-marketing:ad`); launch-day community posts (Product Hunt / Show HN) → community-launch-runner via `/aaron-marketing:launch`. Comment/DM/mention triage & UGC permission → engagement-inbox-manager; listening / share of voice / dark-social → `/aaron-marketing:social --phase observe`; creator deliverable review → creator-content-auditor via `/aaron-marketing:influencer`.
• **Narrative = message, not medium**: durable brand message (what to say / positioning / message house / voice / boilerplate / strategic narrative) → `/aaron-marketing:narrative`; a *single launch's* positioning canvas + PR-FAQ → positioning-mapper / message-house-builder via `/aaron-marketing:launch` (they read the canon when it exists); *per-channel* voice → voice-dossier-builder / channel-registry via `/aaron-marketing:social`; machine-facing entity facts → entity-registry; finished surface copy → each discipline's creative builder (content-writer / ad-creative-builder / email-creative-builder / social-creative-builder); "is it landing / are we drifting" → `/aaron-marketing:narrative --phase evaluate`.

Rules

• Follow the routing contract in [references/aaron-product-api-contract.md](../references/aaron-product-api-contract.md), then read the small [routing-shard index](../references/auto-routing-scenarios.md) (both under the plugin root — resolve against `${CLAUDE_PLUGIN_ROOT}` when installed). Load exactly one primary discipline shard after lightweight triage. Add the cross-discipline shard only for a real boundary ambiguity; add a second discipline shard only for a concrete handoff. Load at most **3 shards total** and never load the full shard directory speculatively. Natural-language auto-invocation is host-dependent unless `/aaron-marketing:auto` is explicit. For influencer goals, route to the matching influencer skill by name or `/aaron-marketing:influencer` phase; for paid-ads goals, route to the matching ROAS-phase skill by name or `/aaron-marketing:ad` phase; for email goals, route to the matching SEND-phase skill by name or `/aaron-marketing:email` phase; for product-launch goals, route to the matching RAMP-phase skill by name or `/aaron-marketing:launch` phase; for organic-social goals, route to the matching ECHO-phase skill by name or `/aaron-marketing:social` phase; for brand-narrative & messaging goals, route to the matching TALE-phase skill by name or `/aaron-marketing:narrative` phase (`/aaron-marketing:seo-geo` covers SEO/GEO only). Only clearly non-marketing work stops with a pack-boundary note — influencer, paid, email, launch, social, and narrative goals are in scope and are routed, never declined.
• **Memory-management exemption**: memory-management lifecycle operations (query, archive, restore, purge) operate on user-owned project memory regardless of topical scope and are NOT subject to the pack-boundary check; safety is enforced by per-operation user confirmation.
• Algorithm: parse the goal -> assign the closest scenario family -> attach risk gates -> choose the smallest `/aaron-marketing:seo-geo` phase (survey / implement / tune / evaluate), `/aaron-marketing:influencer` phase, `/aaron-marketing:ad` phase, `/aaron-marketing:email` phas