Internal Narrative
Structure investor updates, pitches, and strategy memos with SCR and problem-solution-evidence frameworks so messaging stays honest and compelling.
Overview
Internal-narrative is an agent skill most often used in Validate (also Launch, Grow) that applies SCR and problem-solution-evidence frameworks to credible business storytelling.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill internal-narrativeWhat is this skill?
- SCR framework: Situation, Complication, Resolution (Pyramid Principle style) with investor-update example
- Problem-Solution-Evidence structure for pitches and product announcements
- Emphasizes acknowledging setbacks directly before presenting resolution
- Templates separate external pitch narrative from internal operating narrative consistency
- Reference frameworks section for building compelling, consistent business narratives
- Documents at least 2 major frameworks: SCR and Problem-Solution-Evidence
- SCR example cites concrete figures (e.g. €650K ARR target, €90K combined delayed deals)
Adoption & trust: 519 installs on skills.sh; 17.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have metrics and milestones but your updates sound defensive or rambling, so investors and customers cannot follow the arc of what changed and what you did about it.
Who is it for?
Solo SaaS founders drafting investor emails, strategy posts, or launch copy who need consistent structure without a comms team.
Skip if: Pure technical API documentation, legal disclosures that must follow fixed statutory wording, or fiction creative writing.
When should I use this skill?
User needs investor updates, pitches, product announcements, or internal strategy communications with consistent narrative structure.
What do I get? / Deliverables
You produce tight SCR or problem-solution-evidence narratives that state facts, name complications plainly, and land resolutions before objections form.
- SCR-structured update or memo draft
- Problem-solution-evidence pitch or announcement outline
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Validate is the canonical shelf because narrative clarity defines scope—what problem you solve and why now—before heavy build spend. Scope fits framing the situation, complication, and resolution stakeholders must agree on prior to prototype or full implementation commitments.
Where it fits
Frame a pre-build positioning memo as SCR so advisors agree on the complication before you commit to a MVP scope.
Announce a feature using problem-solution-evidence so launch posts lead with the broken status quo, not feature bullet fluff.
Send a quarterly investor note that names slipped ARR deals as the complication and documents signed recovery as resolution.
Draft audience-specific story variants that keep the same SCR spine while tuning evidence for technical versus business readers.
How it compares
Structured narrative frameworks for business truth-telling—not generic SEO blog templates or social hashtag playbooks.
Common Questions / FAQ
Who is internal-narrative for?
Indie builders and micro-teams who write their own investor, board, and customer-facing story and want repeatable frameworks instead of one-off prompts.
When should I use internal-narrative?
Use in Validate/scope for pitch and positioning memos; Launch/distribution for product announcements; Grow/lifecycle for investor or customer updates that must explain misses and next steps.
Is internal-narrative safe to install?
It supplies writing frameworks only—review the Security Audits panel on this Prism page; avoid pasting confidential figures into untrusted agent sessions.
SKILL.md
READMESKILL.md - Internal Narrative
# Narrative Frameworks Reference frameworks for building compelling, consistent business narratives. --- ## 1. Storytelling Structure for Business ### The SCR Framework (Situation, Complication, Resolution) Barbara Minto's Pyramid Principle adapted for business narrative. Works for any audience. **Situation:** The established facts everyone agrees on. **Complication:** What changed, what problem arose, what makes the situation untenable. **Resolution:** What you're doing about it, and why this solution works. **Example — Investor update:** > **Situation:** We entered Q2 with €650K ARR and a target of €800K. Our DACH pipeline was strong at 3x coverage. > > **Complication:** Two large deals (€90K combined ARR) that were expected to close in May pushed to Q3 due to procurement delays on the customer side. We ended Q2 at €710K — below target but within the range we'd flag as manageable. > > **Resolution:** Both deals are now signed with June start dates. We're entering Q3 at €800K ARR. We've added a new procurement risk flag to our pipeline methodology to catch this pattern earlier. **Why it works:** It respects the audience's intelligence, acknowledges the problem directly, and frames your response before they can object. --- ### The Problem-Solution-Evidence Structure Best for pitches, product announcements, and strategy communications. 1. **The world as it is:** What's the current reality? 2. **What's broken about it:** Why is the status quo painful or inefficient? 3. **What we're doing:** Your specific solution 4. **Why it works:** Evidence, mechanism, or proof 5. **What happens next:** Call to action or forward look **Example — All-hands strategy communication:** > The world as it is: We have 80 customers in DACH. Churn is 8% annually. That means we're losing 6–7 customers a year just to stay flat. > > What's broken: Our onboarding takes 6 weeks. By week 4, customers haven't seen value yet and they're questioning the decision. We've traced 60% of churn to customers who never completed onboarding. > > What we're doing: We're redesigning onboarding to show the first meaningful mobility report within 48 hours of account activation. > > Why it will work: We ran this with 5 pilot customers in Q2. Time-to-first-value dropped from 4 weeks to 2 days. 4 of 5 expanded their contract within 60 days. > > What happens next: Engineering ships the new onboarding flow by August 15. CS is retrained by August 22. We'll run the new flow with all new customers from September 1 and report back at the October all-hands. --- ## 2. The Founder's Narrative The founder's personal story is one of the most underutilized assets in a startup. Used well, it anchors the company's mission and creates genuine connection. ### The Founder Story Structure **Origin:** What led you to this problem? (Ideally personal — you experienced it, someone you loved experienced it, you couldn't stop thinking about why nobody was solving it) **Insight:** What did you see that others didn't? (Your unique perspective or unfair advantage) **Decision:** The moment you committed. (Specific, not aspirational — "I left my job on March 14" not "I decided to pursue my passion") **What you've learned:** 2–3 honest observations that shaped your approach. (Including what you got wrong) **Where you're going:** Connection from your personal why to where the company is heading. **Example (condensed):** > My mother had a fall in 2018 that broke her hip. She spent 3 months in rehabilitation. The terrifying part: nobody saw it coming. Her doctor had assessed her fall risk 4 months earlier — using a paper questionnaire. I spent two years talking to geriatricians trying to understand why this assessment was still done by hand, on paper, in 2018. The answer: nobody had made it easy enough for a non-specialist to do it digitally. That's what we're building. **Why it matters:** Investors, candidates, and customers all respond to a founder who started from a real problem rath