Founder Report

Founder Report — package synthesis.md into "Your Growth Tactics"

synthesis.md is written to pass a reviewer: it carries disposition tables, traceability lines, pool audits, and self-grades, because downstream checks parse them. That makes it a working paper, not a deliverable. This stage derives the founder view: it reads the APPROVED synthesis.md and re-packages the tactics into growth-tactics.md — the page the founder actually opens first. synthesis.md itself is never modified (its structure is a load-bearing contract with the reviewer and the orchestrator's checks).

The one rule — re-package, never re-author

Zero new content. Every sentence in the output must be traceable to something synthesis.md already says. Specifically:

• No new claims, numbers, estimates, channels, or tactics. If synthesis.md doesn't say it, the report doesn't either.
• Tactic count and names are preserved exactly — same tactics, same order, same names — minus bracket tags: strip the — [Pass 1 White Space] / — [Pass 2 Synergy/Founder-Fit] origin labels from titles, and strip [HIGH COMPLEXITY] / [LOW CONFIDENCE] flags from names. Where such a flag exists, say it in plain words inside the card instead (e.g. "this is the heaviest lift in the set" under What you need).
• Allowed transformations: reorder, merge fields, strip labels and citations, split long sentences, and simplify wording to meet writing-style.md. Nothing else.

Inputs & Output

• WS/03-think-tanks/demand-generation/synthesis.md (PRIMARY — the APPROVED final synthesis; read-only)
• ${CLAUDE_PLUGIN_ROOT}/reference/writing-style.md (the voice contract — grade 6–8, ≤~20 words per sentence, banned-jargon table, the coffee test)
• OUTPUT: WS/03-think-tanks/demand-generation/growth-tactics.md (write no other files)

Document skeleton (exactly these sections, in this order)

1. # Your Growth Tactics

A 2-3 sentence intro: what these tactics are, why they fit THIS founder (pull the budget / team / stage facts from the Synthesis Overview's Constraint Summary), and how to use the document (start with the quick wins, read each card before committing).

2. ## Start this week

The tactics whose first signal arrives within ~4 weeks — take them from the Tactical Clusters quick-wins group. One line each: the tactic name + what you'd do first. No card detail here; the cards follow.

3. ## The tactics

One card per tactic, in synthesis order. Heading: ### N. <Name> (sequential number, plain name, no bracket labels). Each card has exactly these 7 fields, in this order:

"Execute this" rules. This field is the ONE exception to the "zero new content" rule — it names execution aids, not strategic claims. Scope it tightly:

• Name 2-3 concrete tools, agent skills, or templates that help the founder execute the tactic's first steps. Match them to what the tactic actually involves:
  • Outreach / cold email → the cold-email skill (coreyhaines31/marketingskills) or the agent's built-in writing
  • Copy / messaging → the copywriting skill or the agent's built-in writing
  • Landing page / demo → v0.dev, the free-tools skill, or the agent's code generation
  • Community / social → the community-marketing or social skill
  • Content / SEO → the content-strategy or ai-seo skill
  • Design / visual assets → Canva, Figma, or the agent's image generation
  • Tracking / measurement → a simple spreadsheet with columns for the kill-signal metric
• Format as a short bulleted list: → <what>: <tool/skill name>.
• Do NOT invent tactics, channels, or numbers here — only name execution tools.
• If the tactic is purely manual (e.g. "walk into 10 coffee shops"), say → No tools needed — this is a shoes-on-the-ground play.