From dev-gtm
Design authentic stories, recruit and run Technical Advisory Boards (TAB), avoid the 12 most common story mistakes, build dev influencer presence, and define dev-friendly packaging, pricing, and feedback loops for early-stage developer-facing products and startups. Use when working on GTM positioning, launch narratives, TAB outreach, presence strategy, or packaging for devs. Also activates for mentions of "story", "TAB", "12 most common story mistakes", "villain", "sell the category", "authenticity", "presence", "packaging", "pricing for devs", "manager deadline", "ship tonight", "launch story", or "dev gtm".
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-gtm:devrel-story-craftThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design authentic stories, recruit and run TABs, avoid the 12 most common story mistakes, build presence, and define dev-friendly packaging for early-stage developer-facing startups and products. State the area (Story Building, TAB, Presence & Advocacy, Packaging & Pricing) and whether you want review/audit or help planning/generating.
Design authentic stories, recruit and run TABs, avoid the 12 most common story mistakes, build presence, and define dev-friendly packaging for early-stage developer-facing startups and products. State the area (Story Building, TAB, Presence & Advocacy, Packaging & Pricing) and whether you want review/audit or help planning/generating.
| Area | Review / Audit | Plan / Generate |
|---|---|---|
| Story Building | Audit draft for 12 mistakes, villain rule, evidence | Build story canvas, generate TAB questions, rewrite |
| TAB | Review recruitment plan or call synthesis | Plan outreach, draft messages + 3 questions |
| Presence & Advocacy | Audit posts for authenticity / social proof gaps | Plan calendar, generate signature conversations |
| Packaging & Pricing | Review against "magic free" + value metric rules | Define value metric, design free tier + upsell |
For the full synthesized 12 mistakes with fixes, story canvas template, and explicit counters for rationalizations, load
references/story-framework.md.For TAB recruitment principles, the exact 3 diagnostic questions, email templates, call structure, and synthesis process, load
references/tab-playbook.md.For authenticity rules, 80% presence, 3 steps of advocacy, handling haters, and generating signature conversations, load
references/presence-advocacy.md.For "magic should be free", value metric (eliminate wasted time), win-win pricing, transparency, and packaging audit checklist, load
references/packaging-pricing.md.
Review mode: Take the draft. Run it against every one of the 12 mistakes in references/story-framework.md. Flag each violation with the exact "Why bad" + quote the offending sentence. Require a villain statement. Check for evidence. Output a rewritten version only after the audit.
Generate / Plan mode:
Mandatory before any story leaves the room:
Talking about the solution first? Delete the draft and restart with the pain. No exceptions.
Review mode: Audit any recruitment email, list of questions, or synthesis notes against the 3 principles and the exact 3 diagnostic questions in references/tab-playbook.md. If the email leads with your product or the questions are generic ("what do you think?"), flag it as invalid.
Generate / Plan mode:
If you have not run TAB calls, you have no story yet — only a hypothesis.
Review mode: Audit posts, threads, or plans for the authenticity red flags listed in references/presence-advocacy.md. Check that social proof is customer-sourced, not self-claimed. Check that content delivers complete value without bait.
Generate / Plan mode:
Review mode: Run the packaging against the audit checklist in references/packaging-pricing.md. Verify magic (the villain-killer) is free and frictionless to first success. Verify value metric is expressed in reclaimed developer time.
Generate / Plan mode:
Before moving between areas, verify:
Story Building → TAB: The story draft (or canvas) has been reviewed for all 12 mistakes, contains an explicit villain statement, sells the category, and has at least placeholder evidence slots filled from real sources. If the draft talks about features or the company as hero, return to Story Building.
TAB → Presence: At least 5 TAB calls with diverse personas have been completed. The story canvas has been updated with direct quotes. The recruitment email and questions used followed the templates exactly. No public presence or launch material may be generated from an unvalidated story.
Presence → Packaging: The presence plan only amplifies customer/TAB voices and signature conversations derived from the validated story. Packaging review confirms that the "magic" experience promised in the story is actually free and achievable in the proposed packaging.
Any area → Done: The output cites the specific rule or template used from the references. The user can see which mistake was avoided or which principle was followed.
When the user adds time pressure, manager authority, or "just send something tonight" language:
All agents must cite the Rationalization Counter Table in story-framework.md when they feel the urge to shortcut.
Before declaring the session complete for any area:
Inbound triggers:
Outbound handoffs:
docs-writing-style or authoring-cookbooks.devrel-dx-craft then devrel-tooling.agent-plugin-development.devrel-dx-craft.At the end of every session, ask: "Did this solve what you were trying to do?"
Synthesized from the Developer-Facing Startup Alchemist GTM playbook by Adam Frankl (Alchemist Accelerator, 2024) plus cross-referenced patterns from Developer Marketing Does Not Exist and Technical Content Strategy Decoded. See references/story-framework.md and sibling references for detailed provenance notes. Not a verbatim reproduction; principles and lists have been made actionable for agent use in the devex-kit format.
This skill was authored via writing-skills TDD (RED pressure baselines with subagent dispatches, GREEN minimal content fixing observed failures, REFACTOR with explicit counters, rationalization table, and re-tests).
npx claudepluginhub saif-shines/devex-kit --plugin dev-gtmProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.