mirror of
https://github.com/hanzoai/skills.git
synced 2026-11-19 00:47:36 +00:00
Four MIT collections ported — growthOS, openclaw-marketing-skills, Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45 commands, each naming its origin in its own frontmatter so the tree can be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names appeared in more than one collection and none of the copies were identical; the longest wins, which lands on the more developed text where they genuinely diverge. A fifth collection is deliberately absent. awesome-growth-hacking-skills carries NO licence, which leaves its author every right by default — and it is a list of links rather than a collection of skills, so there is nothing in it to port and no permission to port it with. It is cited as a directory to read. THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing vendor SDKs, running OAuth flows of their own, and ending with long-lived credentials in JSON files under .agents/ and ~/.growthos/ at mode 600. That is a secret on a disk with no rotation path, protected from other users and not from the agent — and one auth implementation per skill. Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect` is the one home for the flow and the platform skills defer to it by provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a tool and a curl cannot disagree. Two had nothing real behind them and now say so. There is no search_console provider, so that skill names what does answer the same questions (google_analytics, google_bigquery) and states that the remedy is a provider in hanzoai/cloud rather than a vendor SDK here. And getxapi-connect was a wrapper around a paid reseller of X's public data with the vendor's key in an env var; it is `listen` now, on our own x connector — a skill named after a vendor makes the vendor the capability and dies with it. The skills referenced paths that only existed inside the source repo, so the shared material they read is ported to reference/ and the paths rewritten. Three skills need the growthOS APPLICATION rather than its data; per the estate's own split an application belongs in hanzoai/ads, social, email or sms as a cloud plugin, so those three say what they need instead of carrying an import that resolves to nothing. Third-party product names are out of our prose and kept in the notices, which is where the licence requires them and the only place they belong. A skill's persona names a role, not somebody else's product. Co-authored-by: Hanzo Dev <[email protected]>
406 lines
31 KiB
HTML
406 lines
31 KiB
HTML
<!doctype html>
|
||
<html lang="en"><head>
|
||
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
|
||
<title>methodology</title>
|
||
<meta name="color-scheme" content="dark">
|
||
<style>
|
||
/* Committed to one visual world: a dark instrument panel. No light variant —
|
||
the dot field and the hairline rules only read on black, and a naive
|
||
inversion would wash both out. Every colour is painted explicitly so the page
|
||
never borrows a host background. */
|
||
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
|
||
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
|
||
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
|
||
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
|
||
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
|
||
|
||
:root{
|
||
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
|
||
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
|
||
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
|
||
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
|
||
--font-zen-pixel-square:'Zen Pixel Square',monospace;
|
||
--mono:var(--font-zen-mono);
|
||
--sans:var(--font-zen-sans);
|
||
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
|
||
--r:999px; --r-soft:14px;
|
||
}
|
||
*{box-sizing:border-box}
|
||
html{-webkit-text-size-adjust:100%}
|
||
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
|
||
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
|
||
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
|
||
|
||
/* The dot field. A halftone made of one repeating radial-gradient, faded out
|
||
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
|
||
/* No overflow clip here: the dot field is inset to the box already, and a clip
|
||
would cut off the copy-prompt menu. */
|
||
.hero{position:relative;border-bottom:1px solid var(--line)}
|
||
.hero::before{content:"";position:absolute;inset:0;
|
||
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
|
||
background-size:7px 7px;
|
||
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
|
||
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
|
||
pointer-events:none}
|
||
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
|
||
|
||
nav{border-bottom:1px solid var(--line)}
|
||
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
|
||
justify-content:space-between;align-items:center;gap:1rem}
|
||
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
|
||
text-transform:uppercase;color:var(--ink);text-decoration:none;
|
||
display:inline-flex;align-items:center;gap:.6rem}
|
||
.brand i{font-style:normal;color:var(--faint)}
|
||
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
|
||
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
|
||
text-transform:uppercase;color:var(--soft);text-decoration:none}
|
||
nav a.up:hover{color:var(--ink)}
|
||
|
||
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
|
||
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
|
||
h1 em{font-style:normal;color:var(--faint)}
|
||
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
|
||
|
||
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
|
||
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
|
||
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
|
||
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
|
||
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
|
||
line-height:1.2;font-weight:400}
|
||
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
|
||
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
|
||
.btn.solid:hover{background:#d8d8d4}
|
||
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
|
||
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
|
||
|
||
/* Copy-prompt selector. Each row copies the prompt for its own target. */
|
||
.copy{position:relative;display:inline-flex}
|
||
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
|
||
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
|
||
padding:.4rem;display:flex;flex-direction:column;
|
||
box-shadow:0 12px 32px rgba(0,0,0,.75)}
|
||
.menu[hidden]{display:none}
|
||
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
|
||
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
|
||
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
|
||
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
|
||
white-space:nowrap}
|
||
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
|
||
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
|
||
.mi:hover .mark{color:var(--ink)}
|
||
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
|
||
letter-spacing:.1em;text-transform:uppercase}
|
||
|
||
/* Works-with bar: one scrolling row, name and mark per agent. */
|
||
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
|
||
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
|
||
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
|
||
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
|
||
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
|
||
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
|
||
display:flex;align-items:center}
|
||
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
|
||
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
|
||
-webkit-overflow-scrolling:touch;
|
||
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
|
||
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
|
||
.bar::-webkit-scrollbar{display:none}
|
||
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
|
||
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
|
||
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
|
||
text-decoration:none;background:var(--ground)}
|
||
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
|
||
.agent .mark{width:.95rem;height:.95rem}
|
||
|
||
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
|
||
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
|
||
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
|
||
p{margin:0 0 1rem;max-width:70ch}
|
||
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
|
||
li{margin:.22rem 0}
|
||
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
|
||
text-decoration-color:var(--line-hi)}
|
||
a:hover{text-decoration-color:var(--ink)}
|
||
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
|
||
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
|
||
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
|
||
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
|
||
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
|
||
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
|
||
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
|
||
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
|
||
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
|
||
display:block;overflow-x:auto}
|
||
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
|
||
|
||
.curl{display:block;background:var(--panel);border:1px solid var(--line);
|
||
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
|
||
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
|
||
white-space:pre;line-height:1.9}
|
||
.curl b{color:var(--ink);font-weight:400}
|
||
.curl i{font-style:normal;color:var(--faint)}
|
||
|
||
/* index */
|
||
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
|
||
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
|
||
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
|
||
#q:focus{outline:none;border-color:var(--soft)}
|
||
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
|
||
text-transform:uppercase;margin:0 0 2rem}
|
||
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
|
||
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
|
||
padding-bottom:.45rem}
|
||
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
|
||
border-radius:var(--r-soft);text-decoration:none}
|
||
.row:hover{background:#0a0a0a}
|
||
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
|
||
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
|
||
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
|
||
color:var(--faint);font-size:.85rem}
|
||
footer a{color:var(--soft)}
|
||
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
|
||
margin:0 0 2rem;font-size:.85rem}
|
||
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
|
||
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
|
||
border-bottom:1px solid var(--line);padding-bottom:.4rem}
|
||
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
|
||
.fmap a:hover{text-decoration:underline}
|
||
.fmap div{color:var(--faint);line-height:1.5}
|
||
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
|
||
|
||
@media (max-width:640px){
|
||
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
|
||
.btns{gap:.5rem}
|
||
.btn{padding:.75rem 1.15rem;font-size:.68rem}
|
||
.copy,.copy .btn{width:100%;justify-content:center}
|
||
.menu{left:0;right:0;min-width:0}
|
||
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
|
||
.strip b{border-right:0;padding-right:0}
|
||
.bar{width:100%}
|
||
}
|
||
</style>
|
||
<link rel="alternate" type="text/markdown" href="/methodology.md">
|
||
|
||
<link rel="icon" href="/favicon.svg">
|
||
<link rel="canonical" href="https://hanzoskills.com/methodology">
|
||
</head>
|
||
<!-- Reading this with a machine? Every page here is also plain markdown.
|
||
This one: https://hanzoskills.com/methodology.md
|
||
Index: https://hanzoskills.com/llms.txt
|
||
Corpus: https://hanzoskills.com/all.md
|
||
Append .md to any path for the markdown twin. -->
|
||
<body>
|
||
<nav><div class="in">
|
||
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
|
||
<a class="up" href="/">All skills</a>
|
||
</div></nav>
|
||
|
||
<div class="wrap">
|
||
<h1>methodology</h1><p class="lede">The three-phase workflow that produces a comprehensive marketing plan.</p><h1>Methodology — How a Marketing Plan Gets Made</h1>
|
||
<p>The three-phase workflow that produces a comprehensive marketing plan. SKILL.md is the orchestration layer; this is the operational detail.</p>
|
||
<h2>Phase 1 — INIT (research + intake)</h2>
|
||
<p><strong>Goal:</strong> Walk into Phase 2 with enough context to draft every section without guessing.</p>
|
||
<h3>Step 1.1 — Set up the plan folder</h3>
|
||
<p>Canonical file layout for every plan:</p>
|
||
<pre><code>~/marketing-plans/{client-slug}/
|
||
├── materials/ # Client-provided files (decks, audit output, brand-voice doc, etc.)
|
||
├── research.md # Written in Phase 1 (INIT)
|
||
├── progress.md # State machine — see Step 1.1.1 for schema
|
||
├── sections/
|
||
│ ├── 01.md # Executive summary (written last, ordered first)
|
||
│ ├── 02.md # Strategic frame
|
||
│ ├── ...
|
||
│ └── 13.md # Measurement, RACI, open decisions, appendix
|
||
└── final_plan.md # Compiled deliverable (Phase 3 output)</code></pre>
|
||
<h3>Step 1.1.1 — <code>progress.md</code> state schema</h3>
|
||
<p>Every plan tracks a single <code>progress.md</code> file at the plan root. It's the source of truth for resumption. Schema:</p>
|
||
<pre><code class="lang-markdown"># {Client} — Marketing Plan Progress
|
||
|
||
phase: init | review | finalize | finalized
|
||
current_section: <number, only meaningful during review phase>
|
||
plan_version: v1
|
||
last_updated: YYYY-MM-DD HH:MM
|
||
|
||
## Sections completed
|
||
- [ ] 2. Strategic frame
|
||
- [ ] 3. Current state
|
||
- [ ] 4. Acquisition
|
||
- [ ] 5. Activation
|
||
- [ ] 6. Retention
|
||
- [ ] 7. Referral
|
||
- [ ] 8. Revenue
|
||
- [ ] 9. 90-day roadmap
|
||
- [ ] 10. 12-month outlook
|
||
- [ ] 11. Marketing operations stack
|
||
- [ ] 12. Tactical idea bank
|
||
- [ ] 13. Measurement, RACI, open decisions, appendix
|
||
- [ ] 1. Executive summary (synthesized last)
|
||
|
||
## Approved artifacts
|
||
sections/02.md, sections/03.md, ... (list as they're written)
|
||
|
||
## Notes
|
||
<any open decisions, blockers, or out-of-band context that aren't in research.md></code></pre>
|
||
<h3>Step 1.1.2 — Resumption decision tree</h3>
|
||
<p>On every invocation, check state in this order:</p>
|
||
<ol><li><strong>No <code>{client-slug}/</code> folder</strong> → fresh plan. Create folder + <code>materials/</code> + empty <code>sections/</code>. Start INIT (Step 1.2).</li><li><strong>Folder exists, no <code>research.md</code></strong> → INIT was interrupted. Resume from Step 1.2.</li><li><strong><code>research.md</code> exists, no <code>progress.md</code></strong> → INIT done, REVIEW not started. Create <code>progress.md</code>, start REVIEW from Section 2.</li><li><strong><code>progress.md</code> exists, <code>phase: review</code></strong> → REVIEW in progress. Resume from <code>current_section</code> (or first unchecked box).</li><li><strong><code>progress.md</code> exists, <code>phase: finalize</code></strong> → FINALIZE was interrupted. Re-run Phase 3.</li><li><strong><code>progress.md</code> exists, <code>phase: finalized</code></strong> → plan is done. <strong>Do not silently overwrite.</strong> Ask the user: <em>"This plan is finalized (v{N}). Want to (a) revise it as v{N+1}, (b) start a fresh plan in a new folder, or (c) re-open a specific section?"</em></li></ol>
|
||
<p>Update <code>phase</code> and <code>last_updated</code> whenever state changes.</p>
|
||
<h3>Step 1.2 — Read existing materials</h3>
|
||
<p>If <code>materials/</code> has files, read all of them. Common drops:</p>
|
||
<ul><li>Pitch deck / investor deck</li><li>Positioning doc / brand voice doc</li><li>Customer research / ICP doc</li><li>App Store metrics / analytics snapshot</li><li>Lifecycle email inventory</li><li>Prior audit output (any scored current-state assessment the team has run)</li><li>SEO research (<code>seo/plan.md</code>, <code>seo/keyword-shortlist.md</code>)</li><li>Kickoff call transcript</li><li>Founder Slack / async notes</li></ul>
|
||
<p>Read everything. Capture key facts to <code>research.md</code> as you go.</p>
|
||
<h3>Step 1.3 — Pull live data where wired</h3>
|
||
<p>If MCPs/APIs are wired for this client, pull:</p>
|
||
<ul><li><strong>Ahrefs</strong> → domain rating, organic keywords, backlinks, top pages, ref domains (per <code>/seo-audit</code> skill)</li><li><strong>GA4 MCP</strong> → traffic by channel, conversion events, retention curves</li><li><strong>Stripe MCP</strong> → MRR, ARR, churn, plan mix, blended LTV by cohort</li><li><strong>App Store Connect</strong> (manual or <code>dev-browser</code>) → install → trial → paid funnel; cohort retention</li><li><strong>Customer.io MCP</strong> → flow inventory, send / open / click / unsubscribe rates</li><li><strong>Shopify</strong> → product page conversion, AOV, repeat rate</li><li><strong>GitHub MCP</strong> → repos inventory, last commit dates, what's stale</li><li><strong>Notion</strong> → internal knowledge directory if exposed</li></ul>
|
||
<p>Don't ask the user to copy/paste data that can be pulled directly.</p>
|
||
<h3>Step 1.4 — Conduct structured intake</h3>
|
||
<p>For every gap in the materials, ask the user. The minimum intake covers ten topics:</p>
|
||
<h4>Intake 1 — Client overview</h4>
|
||
<ul><li>What does the company do, in one sentence (founder's words)?</li><li>What's the primary product?</li><li>What other products / SKUs / tiers exist?</li><li>Is the product live, beta, or pre-launch?</li><li>If beta: throttling? GA timeline?</li></ul>
|
||
<h4>Intake 2 — ICP</h4>
|
||
<ul><li>Who are you for, in one sentence?</li><li>What do they say they want?</li><li>What do they actually want?</li><li>What's their stated problem? Their real problem?</li><li>Demographics / firmographics: who fits the ICP exactly?</li></ul>
|
||
<h4>Intake 3 — Funnel state today</h4>
|
||
<ul><li>What are the current funnel numbers? (signups, activations, paid, retention)</li><li>What's the funnel <em>shape</em> — is it bottle-necked at top, middle, or bottom?</li><li>What's the biggest leak?</li></ul>
|
||
<h4>Intake 4 — Funding state</h4>
|
||
<ul><li>Current round (pre-seed / seed / Series A / etc.)?</li><li>Total raised to date?</li><li>Current burn / runway?</li><li>Active raise? Closing when?</li><li>Investors of note?</li><li>Permission to mention fCMO engagement in pitches?</li></ul>
|
||
<h4>Intake 5 — Team</h4>
|
||
<ul><li>Founders and what each owns (product, marketing, sales, etc.)?</li><li>Other roles on the team and their marketing surface area?</li><li>Advisors who touch marketing?</li><li>Agencies / contractors / fractionals?</li><li>Where are the obvious gaps?</li><li>For the team's current marketing owner (if there is one): is the shape π-shaped (two deep skill sets), T-shaped (one deep, broad), or tactical-only? See <code>team-and-agency-model.md</code> for the framework that informs Section 11 RACI and the first-hire recommendation in Section 9.</li></ul>
|
||
<h4>Intake 6 — Budget</h4>
|
||
<ul><li>Current monthly marketing spend, broken down: paid acquisition, tools, retainers, headcount?</li><li>Budget tier this maps to (see <code>funding-stage-unlocks.md</code>)?</li><li>What budget unlocks when the next round closes?</li><li>Blended CAC if known (including salaries, content costs, tools, retainers — not just paid ad spend). If unknown, flag as the top Section 13 open decision — every revenue projection depends on it.</li><li>ARPC, annual retention rate (or churn rate), so the budget math in <code>budget-planning.md</code> can be applied to Section 8 (Revenue) and Section 10 (12-month outlook).</li></ul>
|
||
<h4>Intake 7 — Channels currently active</h4>
|
||
<ul><li>Acquisition: organic SEO, paid search, paid social, content, social, partnerships, events, PR, ambassadors, etc. — for each, status (live / paused / never tried)</li><li>Activation: onboarding state, signup flow, paywall, first-session experience, app store listing</li><li>Retention: lifecycle email state, in-app upsells, churn cohort</li><li>Referral: program existence, attribution, inbound interest</li><li>Revenue: pricing structure, plan mix, recent experiments</li></ul>
|
||
<h4>Intake 8 — Already done</h4>
|
||
<p>What past work should this plan acknowledge?</p>
|
||
<ul><li>Major launches and dates</li><li>PR moments and who covered</li><li>Content pillars / hubs / cornerstone pieces</li><li>Partnerships</li><li>Awards / certifications</li><li>Notable customers / users (if consumer-named users)</li><li>Past advisors / fractionals</li></ul>
|
||
<h4>Intake 9 — In-flight and stuck</h4>
|
||
<ul><li>What's drafted but not shipped? Why?</li><li>What's been "almost ready" for months?</li><li>What's blocking each?</li><li>What's broken or actively harmful?</li></ul>
|
||
<h4>Intake 10 — Strategic posture</h4>
|
||
<ul><li>The most important thing to fix this quarter (founder's read)</li><li>The most important thing to ignore this quarter (founder's read)</li><li>What investors / board are asking about most</li><li>Any constraints not visible elsewhere (legal, partnership-related, brand-related)</li></ul>
|
||
<h3>Step 1.5 — Score current state against the rubric</h3>
|
||
<p>Use the 17-section rubric in <code>references/current-state-rubric.md</code> as your scoring lens. Two modes:</p>
|
||
<ul><li><strong>From rich materials.</strong> When the team has shared decks, prior content audits, an existing brand voice doc, recent positioning work, or a kickoff call transcript — score from those. Mark "scored from materials" in the section heading.</li><li><strong>From a separately scored audit.</strong> If the team already has a scored current-state assessment (in any format), ingest those numbers directly. Don't redo the work.</li></ul>
|
||
<p>Either way, the output is the scored 17-row table that becomes Section 3 of the plan, followed by a 2–4 sentence "shape interpretation" calling out where strengths and gaps cluster.</p>
|
||
<h3>Step 1.6 — Write research.md</h3>
|
||
<p>Compile everything into <code>research.md</code> with this structure:</p>
|
||
<pre><code class="lang-markdown"># {Client} — Marketing Plan Research Record
|
||
|
||
**Date:** YYYY-MM-DD
|
||
**Author:** (fCMO / planner name)
|
||
|
||
## Company snapshot
|
||
- One-sentence description
|
||
- Stage (pre-seed / seed / Series A / etc.)
|
||
- Product status (beta / GA)
|
||
|
||
## ICP
|
||
- Primary ICP
|
||
- Stated vs. actual problem
|
||
- Demographics / firmographics
|
||
|
||
## Funnel state today
|
||
- Current numbers
|
||
- Funnel shape
|
||
- Biggest leak
|
||
|
||
## Funding
|
||
- Total raised
|
||
- Current round status
|
||
- Runway
|
||
|
||
## Team
|
||
- Founders and ownership
|
||
- Marketing surface area by person
|
||
- Gaps
|
||
|
||
## Current marketing budget
|
||
- $/mo total
|
||
- Breakdown
|
||
- Tier mapping
|
||
|
||
## Channels currently active
|
||
[By AARRR stage]
|
||
|
||
## Already done (acknowledge in plan)
|
||
[List]
|
||
|
||
## In-flight and stuck
|
||
[List with blockers]
|
||
|
||
## Strategic posture
|
||
- Founder's top priority
|
||
- Founder's top de-prioritization
|
||
- Investor pressure points
|
||
- Constraints
|
||
|
||
## Current-state rubric scores
|
||
[17 section scores using `references/current-state-rubric.md`. If a prior scored audit exists, paste those scores. Otherwise mark "scored from materials."]
|
||
|
||
## Materials read
|
||
[List of files in materials/ + when read]</code></pre>
|
||
<p>Save. Move to Phase 2.</p>
|
||
<hr>
|
||
<h2>Phase 2 — REVIEW (section-by-section drafting)</h2>
|
||
<p><strong>Goal:</strong> Walk through all 13 sections of the plan template (<code>references/plan-template.md</code>), drafting each, getting user confirmation, saving as you go.</p>
|
||
<h3>Step 2.1 — Initialize progress.md</h3>
|
||
<p>Use the schema defined in Step 1.1.1 above. Set <code>phase: review</code>, <code>current_section: 2</code>, <code>plan_version: v1</code>, and stamp <code>last_updated</code>.</p>
|
||
<h3>Step 2.2 — Walk each section in this order: 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, then 1</h3>
|
||
<p>Section 1 (Executive Summary) is drafted <strong>last</strong> because it depends on every other section's conclusions. Walk Sections 2 → 13 in numeric order, then synthesize Section 1 from the others. The final compiled <code>final_plan.md</code> is always presented in canonical order 1 → 13.</p>
|
||
<p>For each section, use the template at <code>references/plan-template.md</code> to draft. Then in chat:</p>
|
||
<ol><li>Present the draft (or key bullets — short sections inline, long sections as bullet outline first)</li><li>Ask: <em>"Approve, adjust, or expand?"</em></li><li>Iterate until user confirms</li><li>Save the confirmed text to <code>sections/01.md</code> ... <code>sections/13.md</code> (one file per section, zero-padded for sort order). This is the canonical persisted artifact — recovery depends on it.</li><li>Check the box in <code>progress.md</code></li><li>Move to next section</li></ol>
|
||
<h3>Step 2.3 — Section-specific guidance</h3>
|
||
<p><strong>Section 1 (Executive summary)</strong> is synthesized from Sections 2–13 after they're all approved. Draft it last; present it first in the output document.</p>
|
||
<p><strong>Section 3 (Current state)</strong> uses the embedded 17-section rubric in <code>references/current-state-rubric.md</code>. If a prior scored audit exists, paste those scores in. If not, score from available materials.</p>
|
||
<p><strong>Sections 4–8 (AARRR)</strong> each follow the same internal structure: current state, the plan (numbered moves), 90-day moves, 12-month outlook, skills + tools. Don't skip the skills + tools sub-section — it's what makes the plan operationally honest.</p>
|
||
<p><strong>Section 11 (Marketing operations stack)</strong> is auto-generatable from <code>references/ops-stack-mapping.md</code> plus the specific moves named in Sections 4–8.</p>
|
||
<p><strong>Section 12 (Idea bank)</strong> is auto-generatable from <code>references/idea-cross-reference.md</code> plus client-specific filters (skip ideas that conflict with brand voice; status moves based on funding-stage timing).</p>
|
||
<p><strong>Section 13</strong> lives at the end. Open decisions should be ranked by impact. Appendix should reference only files the team can access (warn about machine-local paths).</p>
|
||
<h3>Step 2.4 — Brand voice consistency</h3>
|
||
<p>If the client has documented brand voice rules (captured in research.md / Section 2), every section must respect them. Common voice constraints:</p>
|
||
<ul><li>Vocabulary rules (YES / NO lists)</li><li>CTA rules (e.g., "never pressure")</li><li>Initiatory vs. explanatory framing</li><li>Tone (e.g., authoritative-yet-accessible, intimate-yet-professional)</li></ul>
|
||
<p>If a section's draft violates the brand voice, redo it before showing it to the user.</p>
|
||
<hr>
|
||
<h2>Phase 3 — FINALIZE (compile + verify + publish)</h2>
|
||
<p><strong>Goal:</strong> Produce <code>final_plan.md</code> and optionally publish to a shared repo.</p>
|
||
<h3>Step 3.1 — Compile</h3>
|
||
<p>Set <code>phase: finalize</code> in <code>progress.md</code> before starting. Concatenate <code>sections/01.md</code> through <code>sections/13.md</code> into <code>final_plan.md</code> (canonical order 1 → 13, regardless of drafting order). Add:</p>
|
||
<ul><li>Title header with date and "v1" version marker</li><li>"Prepared by / For / Date / Status" frontmatter</li><li>Section anchors that work in Notion paste</li></ul>
|
||
<h3>Step 3.2 — Verification pass</h3>
|
||
<p>Before printing:</p>
|
||
<ul><li><strong>Cross-reference check</strong> — every marketing-ideas number (e.g., "idea #17") matches the actual idea in <code>references/idea-cross-reference.md</code>. Every related-skill mention either exists in the <code>marketingskills</code> repo or is documented as an external dependency (see ops-stack-mapping note on cross-marketplace skills).</li><li><strong>MCP/API check</strong> — every tool mentioned in Section 11 actually exists in the user's stack (per research.md intake) OR is flagged as "future / not yet wired."</li><li><strong>Path check</strong> — no machine-specific paths (<code>/Users/...</code>, <code>/home/...</code>) in the output. Replace with descriptive references.</li><li><strong>Voice check</strong> — final read against brand voice rules. Flag and fix violations.</li><li><strong>Open-decisions check</strong> — every "TBD" or unanswered question from intake is listed in Section 13's open decisions, not hidden in the body.</li><li><strong>Acknowledge check</strong> — every item from "already done" in research.md is acknowledged somewhere in the plan.</li></ul>
|
||
<h3>Step 3.3 — Print</h3>
|
||
<p>Output <code>final_plan.md</code> to the plan folder. Print a summary to chat:</p>
|
||
<blockquote><p><em>"Marketing Plan v1 saved to <code>~/marketing-plans/{client-slug}/final_plan.md</code>. ~X,XXX words across 13 sections. Ready to paste into Notion or share with the team."</em></p></blockquote>
|
||
<h3>Step 3.4 — Publish (optional)</h3>
|
||
<p>Ask the user:</p>
|
||
<blockquote><p><em>"Want me to publish this to a shared GitHub repo so the team can access it? If yes, what's the target repo and path (e.g., <code>{client-org}/{client-context}/marketing/plan.md</code>)?"</em></p></blockquote>
|
||
<p>If yes:</p>
|
||
<ul><li>Clone (or assume cloned) target repo</li><li>Check out a feature branch or push direct to main per user's preference</li><li>Copy <code>final_plan.md</code> to the target path</li><li>Adjust the appendix to use repo-relative paths (not machine paths)</li><li>Commit + push</li><li>Confirm with commit URL</li></ul>
|
||
<p>If no: leave it local. Done.</p>
|
||
<h3>Step 3.5 — Mark finalized</h3>
|
||
<p>Set <code>phase: finalized</code> in <code>progress.md</code> and stamp <code>last_updated</code>. This is the terminal state and prevents future <code>/marketing-plan</code> invocations from silently overwriting the plan (see Step 1.1.2 case 6).</p>
|
||
<hr>
|
||
<h2>Resuming a plan</h2>
|
||
<p>Resumption is governed entirely by the decision tree in Step 1.1.2 above — always check state in that order on every invocation.</p>
|
||
<p>If the user says <em>"start over"</em> → ask whether they want to delete the existing folder or move it to <code>archive/</code> first; don't silently overwrite. If the user says <em>"redo Section X"</em> → uncheck that box in <code>progress.md</code>, delete <code>sections/0X.md</code>, and re-draft.</p>
|
||
<h2>Failure modes to watch for</h2>
|
||
<ul><li><strong>Skipping intake.</strong> A plan written without proper intake is generic and won't survive contact with the founder. Always do the full ten-topic intake unless the user explicitly waives it.</li><li><strong>Pretending data exists.</strong> If you can't confirm a number (current MRR, retention rate, etc.), don't guess. Mark it <code>[TBD — to confirm with team]</code> in the plan and add to open decisions.</li><li><strong>Ignoring the brand voice.</strong> If the client has a strong voice (most do), every section must respect it. Read the voice rules before drafting any copy-adjacent text.</li><li><strong>Padding the idea bank.</strong> Section 12 is comprehensive only if it includes the skip list with reasons. Don't pad with ideas that clearly don't fit just to hit the 139.</li><li><strong>Glossing over uncomfortable metrics.</strong> If churn is high or activation is low, name it in Current State. Founders read past sugar-coating.</li><li><strong>Forgetting funding-stage logic.</strong> If the client is mid-raise, the plan must explain what changes when the round closes. Skipping this turns a plan into a wish-list.</li></ul>
|
||
<footer>
|
||
<div class="fmap">
|
||
<div><b>Build</b>
|
||
<a href="https://hanzo.app">hanzo.app</a> app builder
|
||
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
|
||
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
|
||
<div><b>Run</b>
|
||
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
|
||
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
|
||
<div><b>Account</b>
|
||
<a href="https://hanzo.id">hanzo.id</a> sign in
|
||
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
|
||
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
|
||
<div><b>Company</b>
|
||
<a href="https://hanzo.ai">hanzo.ai</a> canonical
|
||
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
|
||
</div>
|
||
<div class="fend"><a href="/methodology.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
|
||
</footer>
|
||
</div></body></html> |