strategy-and-roadmap

Featured

After the founder brief, turn it into an honest diagnosis and a prioritized, stage-aware GTM roadmap saved as docs/gtm-cofounder/gtm-roadmap.md. This is the hub the user returns to every session to see where they are and the single next move. Use right after start-here, whenever the user doesn't know what to work on next, wants a plan instead of a one-off task, or is drowning in disconnected tactics.

AI & Automation 274 stars 27 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
81
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Strategy and roadmap (your plan) > A pile of tactics is not a go-to-market. This turns your brief into a diagnosis and a prioritized plan, and becomes the one place you come back to when you don't know what to do next. **Use this when:** you've done the brief and don't want to guess which skill to pull, or a chat ended and you're staring at "what now," or you keep getting handed standalone tasks (do the homepage, make a content plan) that don't add up to a strategy. ## The core idea The other skills are moves. This is the game plan that decides which move, and when. It does three things: 1. **Diagnose.** Read the brief honestly. Where are you actually strong? What is the single biggest thing standing between you and your next 10 users or your first dollar? Name one bottleneck, not five. 2. **Prioritize by stage.** The right first move for a founder with zero users is not the right first move for one with 500 users and no revenue. Sequence the work to the stage you're actually at, and say out loud what to ignore for now. 3. **Persist.** Write it to `docs/gtm-cofounder/gtm-roadmap.md` so it survives the chat. Next session you read the roadmap, not a dead thread. ## How to run this (for the agent) - **Read `docs/gtm-cofounder/founder-brief.md` first.** If it does not exist, run `start-here` before this. Everything here keys off the brief. - **Lead with a diagnosis, not a task list.** Two or three sentences: here is what's working, here is the one bottleneck that matters...

Details

Author
AIDevGTM
Repository
AIDevGTM/gtm-cofounder
Created
1 months ago
Last Updated
4 days ago
Language
N/A
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

start-here

Interview the user once and write a docs/gtm-cofounder/founder-brief.md that every other skill reads first, so the advice is about their real business, not a textbook. Use this before anything else, or whenever the agent lacks context on the user's product, ICP, market, or stage, or is giving generic GTM advice.

274 Updated 4 days ago
AIDevGTM
AI & Automation Listed

roadmap

Use when the user wants to update the roadmap, build a Now/Next/Later view, reprioritize after new information, decide what moves to make room for a new initiative, shift timelines after a dependency slip, or figure out where a new initiative fits. Forces explicit trade-offs and keeps the roadmap anchored to outcomes, not a feature wishlist.

5 Updated 1 weeks ago
Sidsaladi9
AI & Automation Solid

gtm-content

Content engine strategy for /gtm content <target>. Builds the editorial plan around the buyers' jobs-to-be-done - 3-5 content pillars derived from the project's positioning, a pillar-and-cluster topic map, a publishing cadence sized to the founder's real weekly hours, and the repurposing system that turns each finished piece into a week of distribution. Strategy only - the writing happens in /gtm article and the atomizing in /gtm repurpose. Use when the user wants a content strategy, an editorial plan, or to decide what to write about and how often. Also trigger for "content strategy", "content plan", "editorial plan", "content engine", "what should I blog about", "topic map", "content pillars", or "should I start a blog".

18 Updated 3 weeks ago
adaptico