internal-narrative
Build and maintain one coherent company story across all stakeholder audiences -- employees, investors, customers, candidates, and partners. Covers narrative construction, audience translation, contradiction detection, all-hands design, investor updates, crisis communication, and change management communications. Use when preparing all-hands meetings, investor updates, board presentations, recruiting narratives, crisis communications, or any time narrative consistency matters.
What this skill does
# Internal Narrative Builder **Tier:** POWERFUL **Category:** C-Level Advisory **Tags:** company narrative, internal communications, all-hands, investor updates, crisis communication, change management ## Overview One company. Many audiences. Same truth -- different lenses. The Internal Narrative Builder creates and maintains coherent communication across every stakeholder group. Narrative inconsistency is trust erosion: when employees hear one story and investors hear another, it is not strategic framing -- it is a trust debt that compounds until someone catches it. --- ## Core Principle **The same fact lands differently depending on who hears it and what they need.** "We are shifting resources from Product A to Product B" means: - **Employees:** "Is my job safe? Why are we abandoning what I built?" - **Investors:** "Smart capital allocation -- they are doubling down on the winner." - **Customers (Product A):** "Are they abandoning us?" - **Candidates:** "Decisive leadership -- exciting new focus." - **Partners:** "Does this affect our integration?" Same fact. Five narratives needed. The skill is maintaining truth while serving each audience's actual question. --- ## Framework ### Step 1: Build the Core Narrative One paragraph that every other communication derives from. This is the single source of truth. **Template:** ``` [Company] exists to [mission -- present tense, specific]. We are building [what] because [the problem, stated concretely]. Our approach is [what makes your way different]. We are at [honest description of current state] and heading toward [where you are going, in concrete measurable terms]. ``` **Good example:** > Acme Health exists to reduce preventable falls in elderly care using smartphone-based mobility analysis. We are building an AI diagnostic tool for care teams because current fall risk assessments are subjective, infrequent, and often wrong. Our approach -- using the phone camera during a 10-second walking test -- means no new hardware and no specialist required. We have 80 care facilities in DACH paying us EUR 800K ARR, and we are heading to EUR 3M ARR by demonstrating clinical value at scale before our Series B. **Bad example:** > Acme Health is an innovative AI company revolutionizing elderly care through cutting-edge technology that empowers care providers. The good version is usable. The bad version says nothing. ### Step 2: Audience Translation Matrix Take the core narrative and translate for each audience. Same truth, different frame. | Fact | Employees | Investors | Customers | Candidates | Partners | |------|----------|----------|-----------|-----------|---------| | 80 customers | "Your work matters -- we have proven the model" | "PMF signal, capital efficient growth" | "80 facilities trust us" | "Traction you would be joining" | "Growing ecosystem" | | Pivoted from hardware | "We were honest enough to change course" | "Better unit economics, capital efficient" | "Faster, simpler way to serve you" | "Evidence-based decisions, not ego" | "More accessible integration" | | Missed Q2 revenue | "Here is why, the plan, and how you can help" | "Revenue mix shifted, trailing indicators improving" | [Not shared unless relevant] | [Not shared externally] | [Not shared] | | Hiring fast | "Team is growing, your network matters" | "Headcount aligned to growth plan" | [Only if affects service quality] | "Rocket ship moment" | "Expanding capacity" | **Critical rule:** Different framing is not different facts. "We told investors growth and told employees efficiency" is a contradiction. People talk to each other. ### Step 3: Contradiction Detection Protocol Before any major communication, run this check: **Question 1:** What did we tell investors last quarter about this topic? **Question 2:** What did we tell employees at the last all-hands? **Question 3:** Are these consistent? If not -- which version is true? **Common contradictions to catch:** | Contradiction | Audiences | Why Dangerous | |--------------|-----------|---------------| | "Efficient growth" to investors + "hiring aggressively" to candidates | Investors vs candidates | Candidates talk to investors at events | | "Strong pipeline" to investors + "sales is struggling" at all-hands | Investors vs employees | Board members visit offices | | "Customer-first culture" + decisions clearly prioritizing revenue | External vs internal | Employees see through performative values | | "Stable and growing" to customers + "runway concerns" to board | Customers vs board | Customers hear rumors | | "World-class team" to investors + high turnover internally | Investors vs reality | Due diligence reveals truth | **When you catch a contradiction:** Fix the less accurate version. Communicate the correction explicitly. "Last month I said X. After more analysis, the clearer picture is Y." Correcting yourself before someone catches it builds more trust than being caught. ### Step 4: Communication Cadence | Audience | Format | Frequency | Owner | Key Content | |----------|--------|-----------|-------|-------------| | All employees | All-hands meeting | Monthly | CEO | State of company, wins, challenges, Q&A | | Teams | Team standup/update | Weekly | Team leads | Team-specific progress and blockers | | Investors | Written update | Monthly | CEO + CFO | Metrics, narrative, asks | | Board | Board meeting + memo | Quarterly | CEO | Strategy, financials, key decisions | | Customers | Product updates | Per release | CPO / CS | What changed, what is coming | | Candidates | Careers page + interviews | Ongoing | CHRO + Founders | Why join, culture, mission | | Partners | Business review | Quarterly | BD / Partnerships | Joint metrics, roadmap alignment | ### Step 5: All-Hands Design The all-hands is the most important recurring internal communication. Most companies get it wrong. **Structure (60 minutes):** | Segment | Duration | Content | |---------|----------|---------| | State of the company | 10 min | Honest assessment -- good and bad | | Key metrics | 5 min | 3-5 metrics everyone should know, with context | | Wins and recognition | 10 min | Connect team work to company outcomes | | Challenges and plan | 10 min | What is not working and what we are doing about it | | Strategic update | 10 min | Where we are headed and why | | Open Q&A | 15 min | Unscreened, unfiltered questions | **All-Hands Principles:** 1. Lead with honest state. No spin. Employees detect inauthenticity instantly. 2. Connect metrics to people: "Sarah's team shipped X, which drove Y." 3. Give people a reason to be proud of their choice to work here. 4. Leave real time for Q&A -- not curated questions, not "any quick questions?" 5. Follow up on unanswered questions within 48 hours. **All-Hands Failure Modes:** | Failure | Signal | Fix | |---------|--------|-----| | CEO monologue | 55 of 60 minutes is one person talking | Max 30 min presentation, rest is interactive | | Sunshine and rainbows | Only good news, every metric is "great" | Include one honest challenge and its plan | | Metrics without context | "ARR grew 15%" with no benchmark | Always: metric + context + what it means | | Deflected questions | "Great point, let's follow up" (never followed up) | Answer or commit to written follow-up by date | | No employee voice | Leadership talks, employees listen | Include team demos, recognition, Q&A | | Slides over substance | 50 slides of bullet points | Max 15 slides, mostly visuals and charts | ### Step 6: Investor Update Template Monthly investor updates should be concise, honest, and actionable. ``` Subject: [Company] Monthly Update - [Month Year] TL;DR: [One sentence -- honest state of things] METRICS: MRR/ARR: $[X] ([+/-Y]% MoM) Burn: $[X]/month Runway: [X] months Key Metric: [Your North Star] at [value] WINS: - [Specific win with context] - [Specific win with context] CHALLENGES: - [Honest challenge with your plan to address it] ASKS: - [Specific ask: intro, hire
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.