[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75JS9BVYFECZ8KB7YAZKJAR":3,"skill-same:01M75JS9BVYFECZ8KB7YAZKJAR":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75JS9BVYFECZ8KB7YAZKJAR","stress-test",null,"\u002Fem -stress-test — Business Assumption Stress Testing","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fstress-test\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"stress-test\"\ndescription: \"\u002Fem -stress-test — Business Assumption Stress Testing\"\n---\n\n# \u002Fem:stress-test — Business Assumption Stress Testing\n\n**Command:** `\u002Fem:stress-test \u003Cassumption>`\n\nTake any business assumption and break it before the market does. Revenue projections. Market size. Competitive moat. Hiring velocity. Customer retention.\n\n---\n\n## Why Most Assumptions Are Wrong\n\nFounders are optimists by nature. That's a feature — you need optimism to start something from nothing. But it becomes a liability when assumptions in business models get inflated by the same optimism that got you started.\n\n**The most dangerous assumptions are the ones everyone agrees on.**\n\nWhen the whole team believes the $50M market is real, when every investor call goes well so you assume the round will close, when your model shows $2M ARR by December and nobody questions it — that's when you're most exposed.\n\nStress testing isn't pessimism. It's calibration.\n\n---\n\n## The Stress-Test Methodology\n\n### Step 1: Isolate the Assumption\n\nState it explicitly. Not \"our market is large\" but \"the total addressable market for B2B spend management software in German SMEs is €2.3B.\"\n\nThe more specific the assumption, the more testable it is. Vague assumptions are unfalsifiable — and therefore useless.\n\n**Common assumption types:**\n- **Market size** — TAM, SAM, SOM; growth rate; customer segments\n- **Customer behavior** — willingness to pay, churn, expansion, referrals\n- **Revenue model** — conversion rates, deal size, sales cycle, CAC\n- **Competitive position** — moat durability, competitor response speed, switching cost\n- **Execution** — team velocity, hire timeline, product timeline, operational scaling\n- **Macro** — regulatory environment, economic conditions, technology availability\n\n### Step 2: Find the Counter-Evidence\n\nFor every assumption, actively search for evidence that it's wrong.\n\nAsk:\n- Who has tried this and failed?\n- What data contradicts this assumption?\n- What does the bear case look like?\n- If a smart skeptic was looking at this, what would they point to?\n- What's the base rate for assumptions like this?\n\n**Sources of counter-evidence:**\n- Comparable companies that failed in adjacent markets\n- Customer churn data from similar businesses\n- Historical accuracy of similar forecasts\n- Industry reports with conflicting data\n- What competitors who tried this found\n\nThe goal isn't to find a reason to stop — it's to surface what you don't know.\n\n### Step 3: Model the Downside\n\nMost plans model the base case and the upside. Stress testing means modeling the downside explicitly.\n\n**For quantitative assumptions (revenue, growth, conversion):**\n\n| Scenario | Assumption Value | Probability | Impact |\n|----------|-----------------|-------------|--------|\n| Base case | [Original value] | ? | |\n| Bear case | -30% | ? | |\n| Stress case | -50% | ? | |\n| Catastrophic | -80% | ? | |\n\nKey question at each level: **Does the business survive? Does the plan make sense?**\n\n**For qualitative assumptions (moat, product-market fit, team capability):**\n\n- What's the earliest signal this assumption is wrong?\n- How long would it take you to notice?\n- What happens between when it breaks and when you detect it?\n\n### Step 4: Calculate Sensitivity\n\nSome assumptions matter more than others. Sensitivity analysis answers: **if this one assumption changes, how much does the outcome change?**\n\nExample: \n- If CAC doubles, how does that change runway?\n- If churn goes from 5% to 10%, how does that change NRR in 24 months?\n- If the deal cycle is 6 months instead of 3, how does that affect Q3 revenue?\n\nHigh sensitivity = the assumption is a key lever. Wrong = big problem.\n\n### Step 5: Propose the Hedge\n\nFor every high-risk assumption, there should be a hedge:\n\n- **Validation hedge** — test it before betting on it (pilot, customer conversation, small experiment)\n- **Contingency hedge** — if it's wrong, what's plan B?\n- **Early warning hedge** — what's the leading indicator that would tell you it's breaking before it's too late to act?\n\n---\n\n## Stress Test Patterns by Assumption Type\n\n### Revenue Projections\n\n**Common failures:**\n- Bottom-up model assumes 100% of pipeline converts\n- Doesn't account for deal slippage, churn, seasonality\n- New channel assumed to work before tested at scale\n\n**Stress questions:**\n- What's your actual historical win rate on pipeline?\n- If your top 3 deals slip to next quarter, what happens to the number?\n- What's the model look like if your new sales rep takes 4 months to ramp, not 2?\n- If expansion revenue doesn't materialize, what's the growth rate?\n\n**Test:** Build the revenue model from historical win rates, not hoped-for ones.\n\n### Market Size\n\n**Common failures:**\n- TAM calculated top-down from industry reports without bottoms-up validation\n- Conflating total market with serviceable market\n- Assuming 100% of SAM is reachable\n\n**Stress questions:**\n- How many companies in your ICP actually exist and can you name them?\n- What's your serviceable obtainable market in year 1-3?\n- What percentage of your ICP is currently spending on any solution to this problem?\n- What does \"winning\" look like and what market share does that require?\n\n**Test:** Build a list of target accounts. Count them. Multiply by ACV. That's your SAM.\n\n### Competitive Moat\n\n**Common failures:**\n- Moat is technology advantage that can be built in 6 months\n- Network effects that haven't yet materialized\n- Data advantage that requires scale you don't have\n\n**Stress questions:**\n- If a well-funded competitor copied your best feature in 90 days, what do customers do?\n- What's your retention rate among customers who have tried alternatives?\n- Is the moat real today or theoretical at scale?\n- What would it cost a competitor to reach feature parity?\n\n**Test:** Ask churned customers why they left and whether a competitor could have kept them.\n\n### Hiring Plan\n\n**Common failures:**\n- Time-to-hire assumes standard recruiting cycle, not current market\n- Ramp time not modeled (3-6 months before full productivity)\n- Key hire dependency: plan only works if specific person is hired\n\n**Stress questions:**\n- What happens if the VP Sales hire takes 5 months, not 2?\n- What does execution look like if you only hire 70% of planned headcount?\n- Which single person, if they left tomorrow, would most damage the plan?\n- Is the plan achievable with current team if hiring freezes?\n\n**Test:** Model the plan with 0 net new hires. What still works?\n\n### Competitive Response\n\n**Common failures:**\n- Assumes incumbents won't respond (they will if you're winning)\n- Underestimates speed of response\n- Doesn't model resource asymmetry\n\n**Stress questions:**\n- If the market leader copies your product in 6 months, how does pricing change?\n- What's your response if a competitor raises $30M to attack your space?\n- Which of your customers have vendor relationships with your competitors?\n\n---\n\n## The Stress Test Output\n\n```\nASSUMPTION: [Exact statement]\nSOURCE: [Where this came from — model, investor pitch, team gut feel]\n\nCOUNTER-EVIDENCE\n• [Specific evidence that challenges this assumption]\n• [Comparable failure case]\n• [Data point that contradicts the assumption]\n\nDOWNSIDE MODEL\n• Bear case (-30%): [Impact on plan]\n• Stress case (-50%): [Impact on plan]\n• Catastrophic (-80%): [Impact on plan — does the business survive?]\n\nSENSITIVITY\nThis assumption has [HIGH \u002F MEDIUM \u002F LOW] sensitivity.\nA 10% change → [X] change in outcome.\n\nHEDGE\n• Validation: [How to test this before betting on it]\n• Contingency: [Plan B if it's wrong]\n• Early warning: [Leading indicator to watch — and at what threshold to act]\n```\n","# \u002Fem:stress-test — Business Assumption Stress Testing\n\n**Command:** `\u002Fem:stress-test \u003Cassumption>`\n\nTake any business assumption and break it before the market does. Revenue projections. Market size. Competitive moat. Hiring velocity. Customer retention.\n\n---\n\n## Why Most Assumptions Are Wrong\n\nFounders are optimists by nature. That's a feature — you need optimism to start something from nothing. But it becomes a liability when assumptions in business models get inflated by the same optimism that got you started.\n\n**The most dangerous assumptions are the ones everyone agrees on.**\n\nWhen the whole team believes the $50M market is real, when every investor call goes well so you assume the round will close, when your model shows $2M ARR by December and nobody questions it — that's when you're most exposed.\n\nStress testing isn't pessimism. It's calibration.\n\n---\n\n## The Stress-Test Methodology\n\n### Step 1: Isolate the Assumption\n\nState it explicitly. Not \"our market is large\" but \"the total addressable market for B2B spend management software in German SMEs is €2.3B.\"\n\nThe more specific the assumption, the more testable it is. Vague assumptions are unfalsifiable — and therefore useless.\n\n**Common assumption types:**\n- **Market size** — TAM, SAM, SOM; growth rate; customer segments\n- **Customer behavior** — willingness to pay, churn, expansion, referrals\n- **Revenue model** — conversion rates, deal size, sales cycle, CAC\n- **Competitive position** — moat durability, competitor response speed, switching cost\n- **Execution** — team velocity, hire timeline, product timeline, operational scaling\n- **Macro** — regulatory environment, economic conditions, technology availability\n\n### Step 2: Find the Counter-Evidence\n\nFor every assumption, actively search for evidence that it's wrong.\n\nAsk:\n- Who has tried this and failed?\n- What data contradicts this assumption?\n- What does the bear case look like?\n- If a smart skeptic was looking at this, what would they point to?\n- What's the base rate for assumptions like this?\n\n**Sources of counter-evidence:**\n- Comparable companies that failed in adjacent markets\n- Customer churn data from similar businesses\n- Historical accuracy of similar forecasts\n- Industry reports with conflicting data\n- What competitors who tried this found\n\nThe goal isn't to find a reason to stop — it's to surface what you don't know.\n\n### Step 3: Model the Downside\n\nMost plans model the base case and the upside. Stress testing means modeling the downside explicitly.\n\n**For quantitative assumptions (revenue, growth, conversion):**\n\n| Scenario | Assumption Value | Probability | Impact |\n|----------|-----------------|-------------|--------|\n| Base case | [Original value] | ? | |\n| Bear case | -30% | ? | |\n| Stress case | -50% | ? | |\n| Catastrophic | -80% | ? | |\n\nKey question at each level: **Does the business survive? Does the plan make sense?**\n\n**For qualitative assumptions (moat, product-market fit, team capability):**\n\n- What's the earliest signal this assumption is wrong?\n- How long would it take you to notice?\n- What happens between when it breaks and when you detect it?\n\n### Step 4: Calculate Sensitivity\n\nSome assumptions matter more than others. Sensitivity analysis answers: **if this one assumption changes, how much does the outcome change?**\n\nExample: \n- If CAC doubles, how does that change runway?\n- If churn goes from 5% to 10%, how does that change NRR in 24 months?\n- If the deal cycle is 6 months instead of 3, how does that affect Q3 revenue?\n\nHigh sensitivity = the assumption is a key lever. Wrong = big problem.\n\n### Step 5: Propose the Hedge\n\nFor every high-risk assumption, there should be a hedge:\n\n- **Validation hedge** — test it before betting on it (pilot, customer conversation, small experiment)\n- **Contingency hedge** — if it's wrong, what's plan B?\n- **Early warning hedge** — what's the leading indicator that would tell you it's breaking before it's too late to act?\n\n---\n\n## Stress Test Patterns by Assumption Type\n\n### Revenue Projections\n\n**Common failures:**\n- Bottom-up model assumes 100% of pipeline converts\n- Doesn't account for deal slippage, churn, seasonality\n- New channel assumed to work before tested at scale\n\n**Stress questions:**\n- What's your actual historical win rate on pipeline?\n- If your top 3 deals slip to next quarter, what happens to the number?\n- What's the model look like if your new sales rep takes 4 months to ramp, not 2?\n- If expansion revenue doesn't materialize, what's the growth rate?\n\n**Test:** Build the revenue model from historical win rates, not hoped-for ones.\n\n### Market Size\n\n**Common failures:**\n- TAM calculated top-down from industry reports without bottoms-up validation\n- Conflating total market with serviceable market\n- Assuming 100% of SAM is reachable\n\n**Stress questions:**\n- How many companies in your ICP actually exist and can you name them?\n- What's your serviceable obtainable market in year 1-3?\n- What percentage of your ICP is currently spending on any solution to this problem?\n- What does \"winning\" look like and what market share does that require?\n\n**Test:** Build a list of target accounts. Count them. Multiply by ACV. That's your SAM.\n\n### Competitive Moat\n\n**Common failures:**\n- Moat is technology advantage that can be built in 6 months\n- Network effects that haven't yet materialized\n- Data advantage that requires scale you don't have\n\n**Stress questions:**\n- If a well-funded competitor copied your best feature in 90 days, what do customers do?\n- What's your retention rate among customers who have tried alternatives?\n- Is the moat real today or theoretical at scale?\n- What would it cost a competitor to reach feature parity?\n\n**Test:** Ask churned customers why they left and whether a competitor could have kept them.\n\n### Hiring Plan\n\n**Common failures:**\n- Time-to-hire assumes standard recruiting cycle, not current market\n- Ramp time not modeled (3-6 months before full productivity)\n- Key hire dependency: plan only works if specific person is hired\n\n**Stress questions:**\n- What happens if the VP Sales hire takes 5 months, not 2?\n- What does execution look like if you only hire 70% of planned headcount?\n- Which single person, if they left tomorrow, would most damage the plan?\n- Is the plan achievable with current team if hiring freezes?\n\n**Test:** Model the plan with 0 net new hires. What still works?\n\n### Competitive Response\n\n**Common failures:**\n- Assumes incumbents won't respond (they will if you're winning)\n- Underestimates speed of response\n- Doesn't model resource asymmetry\n\n**Stress questions:**\n- If the market leader copies your product in 6 months, how does pricing change?\n- What's your response if a competitor raises $30M to attack your space?\n- Which of your customers have vendor relationships with your competitors?\n\n---\n\n## The Stress Test Output\n\n```\nASSUMPTION: [Exact statement]\nSOURCE: [Where this came from — model, investor pitch, team gut feel]\n\nCOUNTER-EVIDENCE\n• [Specific evidence that challenges this assumption]\n• [Comparable failure case]\n• [Data point that contradicts the assumption]\n\nDOWNSIDE MODEL\n• Bear case (-30%): [Impact on plan]\n• Stress case (-50%): [Impact on plan]\n• Catastrophic (-80%): [Impact on plan — does the business survive?]\n\nSENSITIVITY\nThis assumption has [HIGH \u002F MEDIUM \u002F LOW] sensitivity.\nA 10% change → [X] change in outcome.\n\nHEDGE\n• Validation: [How to test this before betting on it]\n• Contingency: [Plan B if it's wrong]\n• Early warning: [Leading indicator to watch — and at what threshold to act]\n```\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fstress-test",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill stress-test",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill stress-test",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill stress-test","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fstress-test\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]