Chain Estimation Decision Storytelling
Chains estimation, decision analysis, and storytelling to transform uncertain choices into clear, stakeholder-ready recommendations. Quantifies uncertain variables, applies expected value analysis to identify the best option, then packages the analysis into a persuasive narrative. Use when evaluating strategic options (build vs buy, market entry, resource allocation), quantifying tradeoffs, justifying investments, pitching to decision-makers, or when user mentions ROI analysis, expected value, business case, cost-benefit, or needs to combine estimation with persuasive communication.
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill chain-estimation-decision-storytellinggit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/chain-estimation-decision-storytelling ~/.claude/skills/chain-estimation-decision-storytellingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Chain Estimation → Decision → Storytelling ## Table of Contents - [Workflow](#workflow) - [Common Patterns](#common-patterns) - [Guardrails](#guardrails) - [Quick Reference](#quick-reference) Three phases: Estimation (quantify uncertain variables with ranges and probabilities), Decision (apply expected value or scoring to identify best option), Storytelling (package analysis into compelling narrative for stakeholders). **Quick Example:** ```markdown # Should we build custom analytics or buy a SaaS tool? ## Estimation Build custom: $200k-$400k dev cost (60% likely $300k), $50k/year maintenance Buy SaaS: $120k/year subscription, $20k implementation ## Decision Expected 3-year cost: - Build: $300k + (3 × $50k) = $450k - Buy: $20k + (3 × $120k) = $380k - Difference: $70k savings with Buy Expected value with risk adjustment: - Build: 30% chance of 2x cost overrun → $510k expected - Buy: 95% confidence in pricing → $380k expected - Recommendation: Buy (lower cost, lower risk) ## Story "We evaluated building custom analytics vs. buying a SaaS solution. While building seems cheaper initially ($300k vs. $380k over 3 years), custom development carries significant risk—30% of similar projects experience 2x cost overruns, bringing expected cost to $510k. The SaaS solution offers predictable pricing, faster time-to-value (2 months vs. 8 months), and proven reliability. Recommendation: Buy the SaaS tool, saving $130k in expected costs and delivering value 6 months earlier." ```
Details
- Skill name
chain-estimation-decision-storytelling- Repository
- lyndonkl/claude
- Path
skills/chain-estimation-decision-storytelling/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Chain Estimation Decision Storytelling skill do?
Chains estimation, decision analysis, and storytelling to transform uncertain choices into clear, stakeholder-ready recommendations. Quantifies uncertain variables, applies expected value analysis to identify the best option, then packages the analysis into a persuasive narrative. Use when evaluating strategic options (build vs buy, market entry, resource allocation), quantifying tradeoffs, justifying investments, pitching to decision-makers, or when user mentions ROI analysis, expected value, business case, cost-benefit, or needs to combine estimation with persuasive communication.
How do I install the Chain Estimation Decision Storytelling skill?
Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Chain Estimation Decision Storytelling popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/claude
Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
Academic Letter Architect
200lyndonkl/claude
Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
Adr Architecture
200lyndonkl/claude
Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
Check Analogy Novelty
200lyndonkl/claude
Cross-references each proposed analogy in a 5-framing set against substacker shared-context/analogy-catalog.md to flag reuse. Classifies each analogy as new, reused-from-catalog (and which entry), or adjacent-to-catalog (close to an existing entry but not identical). Prevents the writer from recycling "imagine a library" for the twentieth time. Use after generate-analogy-set and before presenting framings to the writer. Trigger keywords — novelty, catalog, analogy reuse, already used, imagine a library.
Ccpa Compliance
213TerminalSkills/skills
Builds California Consumer Privacy Act (CCPA, as amended by CPRA) compliance features: consumer request handling, opt-out of sale/sharing, Global Privacy Control detection and privacy-notice content. Use when serving California users, building privacy features, implementing consumer data rights, or responding to data subject requests.
Claim Extractor
200lyndonkl/claude
Extracts atomic technical claims from a substacker essay draft, converting flowing intuition-first prose into a numbered list where each item is a statement that could in principle be verified or falsified. Skips non-technical sections (personal anecdote, motivation, call-to-action). Use when the Technical Reviewer starts a per-draft review. Trigger keywords — extract claims, atomic claims, technical claim list, fact-check prep.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.