AGENT SKILL

andy-raskin-strategic-narrative

Build or review a buyer-centered strategic narrative using Andy Raskin's public method. Use for sales or investor deck stories, homepage positioning, keynotes, launch narratives, and why-now messaging.

License 许可
Apache-2.0
所属仓库
getedgehq/skills
最近更新
2026-11-12
Stars
★ 5
Forks
0

01 前言 Front Matter

name
andy-raskin-strategic-narrative
description
Build or review a buyer-centered strategic narrative using Andy Raskin's public method. Use for sales or investor deck stories, homepage positioning, keynotes, launch narratives, and why-now messaging.

02 资源文件 7

03 SKILL.md 正文

Andy Raskin Strategic Narrative

Based on Andy Raskin's public method. Not affiliated with or endorsed by Andy Raskin.

When to use

Use this skill when a company needs a coherent story about why buyers must change, what winning now means, and how its offering helps them get there. Typical requests include a sales deck, investor narrative, homepage story, keynote, launch story, or review of an existing pitch. The output is a compact narrative storyboard with evidence and unresolved assumptions, ready to adapt into the requested format.

The buyer is the protagonist. Start with a change in the buyer's world, establish the stakes, define a desirable buyer mission, and introduce capabilities as help with obstacles to that mission. This is also a strategic alignment exercise: the story should influence what the company builds, rather than merely decorate existing differentiators. [S1][S9]

For a narrow copy edit, apply only the relevant checks. Preserve the user's requested deliverable and constraints. A five-part storyboard is this package's drafting aid, not a mandatory slide count prescribed by Raskin. Read the detailed method when constructing or substantially reviewing a narrative; use the examples when the difference between product improvement and a buyer mindset shift is unclear.

Procedure

  1. Define the assignment. Identify the audience, buying context, desired action, format, and available inputs. Separate a customer story from its investor adaptation. Capture these fields in templates/output-template.md before drafting; request missing information only when it materially affects the story.

  2. Gather buyer language and evidence. Read the discovery guidance in references/method.md. Ask what changed that made action urgent, what winning used to mean, and what buyers must achieve now. Distinguish supplied facts, supported inferences, and hypotheses. Mark absent support as [needs source]; never invent customer quotes, statistics, winners, or outcomes.

  3. Identify the change. Use the shift rules in references/method.md. Name the old and new winning mindsets compactly. Check that the change is happening, independent of the seller, and consequential. Reject a product before/after dressed up as a market shift. [S1][S4]

  4. Make the stakes concrete. Follow references/method.md. Describe how adapting creates a positive future and how continuing the old mindset creates a material negative outcome. Use relevant, sourced examples where available; label proposed examples as research gaps. Avoid declaring every slow adopter doomed. [S2]

  5. Locate the enemy. Apply the later clarification in references/method.md: the antagonist is the old mindset. Naming the shift can already name the enemy. Discuss alternatives through their assumptions and suitability, with support for factual comparisons. [S5]

  6. Choose the buyer mission. Use references/method.md to state the future buyers want, without naming ownership of the product as success. Choose the highest useful level that still defines a distinct movement. State who might reasonably reject the mission and what strategic choices it implies. [S7][S12]

  7. Map obstacles to help. Follow references/method.md and the mapping fields in templates/output-template.md. Explain why the mission is difficult, then connect each selected capability to an obstacle. Remove orphan features and promises the offering cannot deliver. [S1][S2]

  8. Select proof. Use references/method.md. Prefer a relevant customer outcome in the customer's voice; otherwise use a demonstration or clearly labeled internal results. Keep proof boundaries visible. Place logos and investor credentials after the story has established relevance. [S1][S2]

  9. Draft the storyboard. Fill templates/output-template.md with compact titles, on-slide text, speaker notes, evidence, and gaps. Compare the transformations in examples/worked-examples.md. Establish the concise narrative before expanding it into prose. [S10]

  10. Tailor and challenge. Apply references/method.md. Keep the shared change while adapting missions, obstacles, and proof by audience. Test comprehension in conversations, record objections, and revise unsupported or untrue pieces. Surface top-message choices for leadership rather than claiming an agent can settle company strategy. [S3][S8][S13]

  11. Review and deliver. Run checklists/review-checklist.md. Resolve failures or explicitly label remaining gaps and their impact. Deliver the requested artifact plus essential evidence notes. Verify method citations against references/sources.md; those sources support the framework, not claims about the user's market.

Files in this skill

04 同仓库更多 Skills

getedgehq
getedgehq/skills

zero-downtime-cloud-move

Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.

★ 5
getedgehq
getedgehq/skills

zayats-ceo-branding

Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.

★ 5
getedgehq
getedgehq/skills

yc-app-roast

YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks "what would a YC partner think", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.

★ 5
getedgehq
getedgehq/skills

yc-app-review

YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press "Send my notes" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.

★ 5
getedgehq
getedgehq/skills

x-growth-playbook

X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says "analyse my X posts", "what works on my Twitter", "how do I grow on X", "what should I post next on X", "audit my X account", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.

★ 5
getedgehq
getedgehq/skills

workplan

Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: "workplan", "work plan", "create a plan", "what's the plan", "where was I", or when Claude detects a multi-step task that needs tracking.

★ 5