Your product lives in the codebase. Your growth strategy lives in Notion, in slide decks, or in conversations you had on a walk. What happens when you move it all into the same repo your agents already read?

The setup is simpler than it sounds. You open Claude Code in your product's repo and answer prompts out loud through Wispr Flow – the agent writes the markdown for you. Every session after that is dual-purpose: it answers the question in front of you AND patches the underlying doc when something turns out to be wrong. The strategy layer self-updates.

This episode walks through bridesmaid.love live – the setup Ben ran with the Pirate Forge cohort last Wednesday. You'll see docs/context/ populate from a founding-interview prompt, a real cookie-consent question turn into a fully-contextualized Linear ticket, and the agent assign next week's work between Ben and Christina from the OKRs alone.

Not theory. A real strategy folder, a real Linear board, and three prompts that ship the entire setup in about an hour.

IN THIS EPISODE

00:00:00 – Why growth strategy belongs in your codebase
00:00:45 – No context, no help
00:02:31 – Half the company's brain was invisible
00:04:51 – Build and grow in one repo (Bridesmaid + Pirate Forge cohort)
00:06:00 – Live: the founding interview that seeds docs/context/
00:07:27 – Inside the strategy folder: business, OKRs, bottlenecks
00:08:20 – The knowledge base that writes itself
00:11:41 – Live demo: a question becomes a Linear ticket
00:16:32 – Strategy that lands in this week's Linear cycle
00:19:40 – Who tackles what – the agent assigns the week
00:23:27 – Run the setup this afternoon: three prompts


DEEP DIVE LINKS

📖 Full Article: https://pirateskills.com/insights/gro...

🎧 Spotify: https://open.spotify.com/show/7kFl0BJ...

🍎 Apple Podcasts: https://podcasts.apple.com/us/podcast...