[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73AZZ2NFMYNNFH46P7MJ7Y4":3,"skill-same:01M73AZZ2NFMYNNFH46P7MJ7Y4":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M73AZZ2NFMYNNFH46P7MJ7Y4","stress-test",null,"\u002Fem -stress-test — Business Assumption Stress Testing","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-stress-test\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fnginity-stress-test","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kalash33\u002Fkstack --skill stress-test",{"tool":38,"command":39},"bunx","bunx skills add kalash33\u002Fkstack --skill stress-test",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill stress-test","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-stress-test\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","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\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]