โ† Back to shop
Team1.2.0

Founder's Growth Stack

Free

Two-agent team for founders who build great things but need help selling them.

toli3 downloads

About

Two-agent team for founders who build great things but need help making the right people know about them. **Chief of Staff** manages strategy and priorities: - Frames strategic context for every marketing initiative - Ensures tactics serve the strategy, not the other way around - Coordinates between your technical work and growth efforts - Maintains priority alignment through compound review cycles **The CMO** handles all marketing execution: - Marketing strategy, audience research, and positioning - Content planning with calendar management - Brand voice development and consistency enforcement - Full copy-suite with 6 format skills and anti-AI humanizer - Creative thinking protocol for campaign ideation **How they work together:** 1. You tell the Chief of Staff what you need 2. CoS frames the strategic context (audience, positioning, constraints) 3. CoS delegates to the CMO with a structured brief 4. CMO develops strategy and content, runs quality checks 5. CoS reviews for strategic alignment and presents to you Covers the gap between "built something great" and "the right people found it."


Tags

foundergrowthmarketingoperationsstrategyteam

README

Install: Founder's Growth Stack

Version: 1.1.0 | Changelog

You are creating a team of 2 agents. Each agent gets its own workspace. The Chief of Staff leads strategy and delegates marketing execution to the CMO. Follow every step below.

Strategy + marketing duo for founders. Chief of Staff handles priorities, decisions, and delegation. CMO handles marketing strategy, content, brand voice, and copy. The CoS coordinates via spawn templates.

Team Members

AgentRoleRecommended Model
Chief of StaffStrategic operations, priorities, delegation, decisionsOpus
The CMOMarketing strategy, content planning, brand voice, copySonnet

Files

agents/
โ”œโ”€โ”€ chief-of-staff/agent/       # Lead agent
โ”‚   โ”œโ”€โ”€ (7 core files)
โ”‚   โ””โ”€โ”€ skills/
โ”‚       โ”œโ”€โ”€ strategic-planning/
โ”‚       โ”œโ”€โ”€ team-coordination/   # Spawn templates for CMO delegation
โ”‚       โ””โ”€โ”€ nightly-compound/
โ””โ”€โ”€ the-cmo/agent/
    โ”œโ”€โ”€ (7 core files)
    โ””โ”€โ”€ skills/
        โ”œโ”€โ”€ marketing-strategy/
        โ”œโ”€โ”€ content-planning/
        โ”œโ”€โ”€ brand-voice-dev/
        โ”œโ”€โ”€ copy-suite/          # 6 format skills + humanizer + research
        โ”œโ”€โ”€ creative-thinking/
        โ””โ”€โ”€ nightly-compound/

Setup Instructions (For the Installing Agent)

1. Name the Team

Ask the user: "What would you like to name each agent? Or I can use defaults (chief-of-staff, cmo)."

2. Check for Conflicts

Read openclaw.json. Search agents.list for any existing agent with chief of staff, operations, marketing, or cmo in its role. If found, ask per-agent: replace, keep both, or cancel.

3. Choose Mode

Ask: "Should the Chief of Staff be your main contact (Direct), or should it run behind an existing agent (Delegated)?"

The Chief of Staff gets Direct mode. The CMO is always Delegated (spawned by the CoS). If Direct: Ask platform. For Telegram: create bot via @BotFather, paste token.

4. Create Workspaces

cp -r agents/chief-of-staff/agent/* ~/.openclaw/workspace-{cos-id}/
cp -r agents/the-cmo/agent/* ~/.openclaw/workspace-{cmo-id}/

OpenClaw auto-discovers skills from each agent's workspace skills/ directory. The skill names in the config (Step 5) must match the folder names inside skills/.

5. Configure Both Agents

Chief of Staff (lead):

{
  "id": "{cos-id}",
  "skills": ["strategic-planning", "team-coordination", "nightly-compound"],
  "subagents": { "allowAgents": ["{cmo-id}"] }
}

CMO:

{
  "id": "{cmo-id}",
  "skills": ["marketing-strategy", "content-planning", "brand-voice-dev", "copy-suite", "creative-thinking", "nightly-compound"],
  "subagents": { "allowAgents": ["*"] }
}

The CMO uses "allowAgents": ["*"] (wildcard) because it may need to spawn creative sub-agents for research, competitive analysis, or copy work on demand. If you prefer tighter control, replace "*" with a scoped list of agent IDs the CMO is allowed to spawn (e.g., ["{cos-id}", "researcher"]).

6. Delegation Wiring

The Chief of Staff's team-coordination skill includes a spawn template for delegating to the CMO. The flow:

  1. User talks to Chief of Staff about a marketing need
  2. CoS frames the strategic context (audience, positioning, constraints)
  3. CoS spawns CMO with a structured brief
  4. CMO develops strategy/content, runs humanizer check
  5. CMO reports back to CoS
  6. CoS reviews strategic alignment and presents to user

7. Vector Memory (Optional)

Check openclaw.json for existing memorySearch config. If already configured, skip this step. If not configured, ask: "Want vector memory search? Requires an OpenAI API key." Recommended for the Chief of Staff. If yes, add memorySearch config. If no, skip.

8. Compound Loops

Set up 2 staggered crons. Ask user's timezone:

AgentTimeFocus
Chief of Staff3:50 AMPriority alignment, decision quality, delegation effectiveness
CMO3:40 AMContent resonance, voice consistency, campaign performance

9. Review and Restart

Show summary of both agents and their configs. Ask for confirmation. Restart gateway once.

10. Verify

Send to the Chief of Staff: "I need to launch a marketing campaign for [ask user for a real product/feature]. Help me plan this."

Confirm:

  • CoS asks strategic questions first (goals, audience, timeline)
  • CoS mentions delegating the content work to the CMO
  • CoS does NOT try to write marketing copy itself

Files included

  • agents/chief-of-staff/agent/AGENTS.md.md
  • agents/chief-of-staff/agent/BOOTSTRAP.md.md
  • agents/chief-of-staff/agent/HEARTBEAT.md.md
  • agents/chief-of-staff/agent/IDENTITY.md.md
  • agents/chief-of-staff/agent/MEMORY.md.md
  • agents/chief-of-staff/agent/skills/nightly-compound/SKILL.md.md
  • agents/chief-of-staff/agent/skills/strategic-planning/SKILL.md.md
  • agents/chief-of-staff/agent/skills/team-coordination/SKILL.md.md
  • agents/chief-of-staff/agent/skills/team-coordination/spawn-templates/cos-to-cmo.md.md
  • agents/chief-of-staff/agent/SOUL.md.md
  • agents/chief-of-staff/agent/TOOLS.md.md
  • agents/chief-of-staff/agent/USER.md.md
  • agents/chief-of-staff/pfp.png.png
  • agents/the-cmo/agent/AGENTS.md.md
  • agents/the-cmo/agent/BOOTSTRAP.md.md
  • agents/the-cmo/agent/HEARTBEAT.md.md
  • agents/the-cmo/agent/IDENTITY.md.md
  • agents/the-cmo/agent/MEMORY.md.md
  • agents/the-cmo/agent/skills/brand-voice-dev/SKILL.md.md
  • agents/the-cmo/agent/skills/content-planning/SKILL.md.md
  • agents/the-cmo/agent/skills/copy-suite/formats/articles-blog.md.md
  • agents/the-cmo/agent/skills/copy-suite/formats/conversion-copy.md.md
  • agents/the-cmo/agent/skills/copy-suite/formats/long-form.md.md
  • agents/the-cmo/agent/skills/copy-suite/formats/social-copy.md.md
  • agents/the-cmo/agent/skills/copy-suite/formats/thread-copy.md.md
  • agents/the-cmo/agent/skills/copy-suite/formats/web-copy.md.md
  • agents/the-cmo/agent/skills/copy-suite/humanizer.md.md
  • agents/the-cmo/agent/skills/copy-suite/references/articles-blog-research.md.md
  • agents/the-cmo/agent/skills/copy-suite/references/conversion-copy-research.md.md
  • agents/the-cmo/agent/skills/copy-suite/references/long-form-research.md.md
  • agents/the-cmo/agent/skills/copy-suite/references/social-copy-research.md.md
  • agents/the-cmo/agent/skills/copy-suite/references/thread-copy-research.md.md
  • agents/the-cmo/agent/skills/copy-suite/references/web-copy-research.md.md
  • agents/the-cmo/agent/skills/copy-suite/SKILL.md.md
  • agents/the-cmo/agent/skills/creative-thinking/SKILL.md.md
  • agents/the-cmo/agent/skills/marketing-strategy/SKILL.md.md
  • agents/the-cmo/agent/skills/nightly-compound/SKILL.md.md
  • agents/the-cmo/agent/SOUL.md.md
  • agents/the-cmo/agent/TOOLS.md.md
  • agents/the-cmo/agent/USER.md.md
  • agents/the-cmo/pfp.png.png
  • pfp.png.png
  • README.md.md

MITSource link coming soonby tolisouls.design