[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F48AF9D2H28F892XGXR3XN":3,"skill-same:01M7F48AF9D2H28F892XGXR3XN":45},{"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":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7F48AF9D2H28F892XGXR3XN","commercialization-risk-classification",null,"Classifies commercialization risks across technical feasibility, regulatory pathway, manufacturing scale, market timing, legal structure, and capital requirements. Maps the full risk landscape and identifies which bottleneck is most likely to derail the commercialization plan. Use when beginning a commercialization strategy assessment, entering a new market vertical, or when a team assumes the path from prototype to market entry is straightforward.","cwik-tech\u002Foctopus","cwik-tech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54542292?v=4","01M7F42E123GEHVK6RWC5MSWJ9","Tomasz Cwik","01M7F42E1PD4P54MTG8PG32VCV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fcommercialization-lead\u002Fskills\u002Fcommercialization-risk-classification\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: commercialization-risk-classification\ndescription: Classifies commercialization risks across technical feasibility, regulatory pathway, manufacturing scale, market timing, legal structure, and capital requirements. Maps the full risk landscape and identifies which bottleneck is most likely to derail the commercialization plan. Use when beginning a commercialization strategy assessment, entering a new market vertical, or when a team assumes the path from prototype to market entry is straightforward.\n---\n\n# Commercialization Risk Classification\n\n## Purpose\n\nCreate a structured map of all commercial risks that could derail the path from prototype to market entry. Identify which constraint is the longest pole in the tent and which hidden dependencies between domains are most fragile.\n\n## When to Use\n\nUse this skill when:\n- Launching a commercialization strategy (intake assessment)\n- Entering a new regulatory domain or market vertical\n- A team assumes the commercialization path is straightforward and risk-free\n- Phases of the roadmap need to be re-scoped because a domain assumption changed\n\n## Risk Domains\n\n### Technical Feasibility\n\n**Questions to press:**\n- Is the prototype proven? At what scale or in what setting?\n- What critical technical unknowns remain? Which are in the critical path to commercialization?\n- How much engineering work is required between prototype and manufacturing-ready design?\n- What technical decisions lock in later choices (regulatory pathway, manufacturing method)?\n- Is the technology patentable, and what is the patent landscape?\n\n**Red flags:**\n- \"We'll solve this in manufacturing.\" (Defers technical risk into the timeline.)\n- \"The prototype works in the lab.\" (But does it work in the customer's environment? Under stress?)\n- Radical innovation in the core technical approach (often signals longer timelines and higher regulatory risk).\n- No clear definition of \"manufacturing-ready design.\"\n\n### Regulatory Pathway\n\n**Questions to press:**\n- What regulatory approvals are required? (FDA clearance, CE mark, PMDA, etc.)\n- Is there a clear precedent for this product class, or is this novel in the regulatory space?\n- What is the expected timeline from dossier submission to approval?\n- What clinical data, manufacturing data, or performance data is required?\n- Are there conditional approval pathways (Breakthrough Device, De Novo, etc.) that could shorten the timeline?\n- What if regulatory rejects the initial submission? What is Plan B?\n\n**Red flags:**\n- \"We think we're Class II, but we haven't asked the regulator yet.\" (Regulatory classification is a critical uncertainty.)\n- \"Clinical data will come from real-world use after launch.\" (May work, but requires post-market surveillance plans.)\n- No precedent for this indication or device class (signals longer timelines and higher uncertainty).\n- Regulatory expertise on the team is thin or missing.\n\n### Manufacturing Scale\n\n**Questions to press:**\n- What is the current manufacturing method? Can it scale, or will a new method be needed?\n- What are the bottlenecks in scaling? Supply chain constraints? Process validation? Quality control?\n- What is the lead time for manufacturing equipment, tooling, or facility buildout?\n- At what volume does the manufacturing method break? When must a new method be adopted?\n- What manufacturing data does regulatory require? When can that validation begin?\n- What is the cost to scale from 1,000 units to 100,000 units? Does that change the business model?\n\n**Red flags:**\n- \"Prototype is hand-assembled; we'll figure out manufacturing later.\" (Manufacturing scale is a major bottleneck and often takes longer than expected.)\n- Single-source suppliers or critical supply chain dependencies with long lead times.\n- Manufacturing validation and regulatory sign-off are treated as separate activities (they are intertwined).\n- No manufacturing lead involved in commercialization strategy.\n\n### Market Timing\n\n**Questions to press:**\n- When does the market window open? Is there a competitive deadline?\n- How long is the market window open? What conditions would close it?\n- Do regulatory timelines align with market opportunity? (Often they don't.)\n- What is the customer's buying cycle? Procurement timeline? Budget cycle?\n- Are there seasonal or economic factors that make certain launch windows better than others?\n- What competitive products are in the pipeline, and when will they launch?\n\n**Red flags:**\n- \"The market is ready now.\" (But regulatory approval takes 18 months.)\n- Market opportunity assumed to last indefinitely (most windows have an expiration date).\n- No customer conversations about adoption timeline or procurement process.\n- Market forecast assumes rapid adoption without evidence of customer pull.\n\n### Legal and Liability Structure\n\n**Questions to press:**\n- What is the liability exposure? Product liability, clinical liability, IP liability?\n- What insurance will be required? How much does it cost? When must it be in place?\n- Are there IP landmines? Patent infringement risk? Trade secret exposure?\n- What is the optimal legal entity structure for commercialization? (Subsidiary, joint venture, licensing agreement?)\n- Are there regulatory bodies that will oversee post-market surveillance or adverse events?\n- What warranties and indemnities will customers require?\n\n**Red flags:**\n- No legal review of the technology or business model.\n- Assumption that \"we'll address liability in Year 2.\" (Insurance and structure must be in place before launch.)\n- Patent landscape not mapped; freedom-to-operate not validated.\n- Terms and liability structure treated as separate from product strategy.\n\n### Capital and Financial Risk\n\n**Questions to press:**\n- What is the total capital required to reach market entry? (Include regulatory, manufacturing, market development.)\n- At what milestone are additional capital raises needed?\n- What runway does the current capital provide?\n- Does the unit economics model hold at launch volume? At scale?\n- What is the break-even volume? When is cash flow positive?\n- Are there milestone-based funding sources (grants, partnerships) that could extend runway?\n\n**Red flags:**\n- \"We'll fund the rest through revenue.\" (Cash flow positive is not realistic until well after launch.)\n- No financial model beyond year 2.\n- Capital requirements wildly underestimated (almost always the case).\n- Financing plan assumes one capital raise; no Plan B if that round fails.\n\n## Bottleneck Identification\n\n**Method:** After mapping all domains, identify the constraint with the longest timeline or the most uncertainty. That constraint determines the overall commercialization timeline — everything else must wait for it.\n\n**Common bottlenecks:**\n- Regulatory approval (almost always): 12–36 months typical.\n- Manufacturing scale-up: 12–24 months from design to production-ready.\n- Market window closure: Competitive or economic factors force a launch deadline.\n- Capital availability: Funding delays or cost overruns delay downstream phases.\n- Clinical data generation: Phase I\u002FII\u002FIII trials add 3–10 years depending on indication.\n\n**Key insight:** The timeline is the maximum of all constraints, not the sum. If regulatory takes 24 months and manufacturing takes 6 months, the total is 24 months — but only if they can overlap. Often they cannot, and the timeline stretches further.\n\n## Hidden Dependencies\n\nEvery domain makes assumptions about what the other domains will deliver. These assumptions are fragile and often wrong.\n\n**Examples of hidden dependencies:**\n- Regulatory pathway assumes technical design is locked (but technical team says design will evolve).\n- Manufacturing assumes regulatory requirements are final (but regulatory often requires manufacturing changes late).\n- Market timing assumes regulatory approval by Q3 (but regulatory is reviewing in parallel and may delay).\n- Capital plan assumes manufacturing will be under budget (but scale-up always costs more than estimated).\n- Clinical trial assumes stable product design (but design often changes during trials).\n\n**Surface these assumptions explicitly and validate each one with the responsible domain owner before proceeding.**\n\n## Output\n\nDelivery a risk map with these sections:\n\n1. **Technical Feasibility:** Current state, critical unknowns in the critical path, lock-in risks.\n2. **Regulatory Pathway:** Classification, expected timeline, precedent (or lack thereof), data requirements.\n3. **Manufacturing Scale:** Current method, bottlenecks, timeline to scale, cost model.\n4. **Market Timing:** Window duration, competitive threats, customer buying cycle, seasonal factors.\n5. **Legal and Liability:** Liability exposure, IP landscape, entity structure, insurance requirements.\n6. **Capital Requirements:** Total capital, milestones, runway, break-even timeline.\n7. **Bottleneck:** Which domain determines the overall timeline.\n8. **Hidden Dependencies:** Assumptions each domain is making about the others; flag the fragile ones.\n9. **Missing Expertise:** What domains are under-represented on the current team?\n10. **Next Step:** What validation or decision must happen before the phased roadmap can be synthesized?\n","# Commercialization Risk Classification\n\n## Purpose\n\nCreate a structured map of all commercial risks that could derail the path from prototype to market entry. Identify which constraint is the longest pole in the tent and which hidden dependencies between domains are most fragile.\n\n## When to Use\n\nUse this skill when:\n- Launching a commercialization strategy (intake assessment)\n- Entering a new regulatory domain or market vertical\n- A team assumes the commercialization path is straightforward and risk-free\n- Phases of the roadmap need to be re-scoped because a domain assumption changed\n\n## Risk Domains\n\n### Technical Feasibility\n\n**Questions to press:**\n- Is the prototype proven? At what scale or in what setting?\n- What critical technical unknowns remain? Which are in the critical path to commercialization?\n- How much engineering work is required between prototype and manufacturing-ready design?\n- What technical decisions lock in later choices (regulatory pathway, manufacturing method)?\n- Is the technology patentable, and what is the patent landscape?\n\n**Red flags:**\n- \"We'll solve this in manufacturing.\" (Defers technical risk into the timeline.)\n- \"The prototype works in the lab.\" (But does it work in the customer's environment? Under stress?)\n- Radical innovation in the core technical approach (often signals longer timelines and higher regulatory risk).\n- No clear definition of \"manufacturing-ready design.\"\n\n### Regulatory Pathway\n\n**Questions to press:**\n- What regulatory approvals are required? (FDA clearance, CE mark, PMDA, etc.)\n- Is there a clear precedent for this product class, or is this novel in the regulatory space?\n- What is the expected timeline from dossier submission to approval?\n- What clinical data, manufacturing data, or performance data is required?\n- Are there conditional approval pathways (Breakthrough Device, De Novo, etc.) that could shorten the timeline?\n- What if regulatory rejects the initial submission? What is Plan B?\n\n**Red flags:**\n- \"We think we're Class II, but we haven't asked the regulator yet.\" (Regulatory classification is a critical uncertainty.)\n- \"Clinical data will come from real-world use after launch.\" (May work, but requires post-market surveillance plans.)\n- No precedent for this indication or device class (signals longer timelines and higher uncertainty).\n- Regulatory expertise on the team is thin or missing.\n\n### Manufacturing Scale\n\n**Questions to press:**\n- What is the current manufacturing method? Can it scale, or will a new method be needed?\n- What are the bottlenecks in scaling? Supply chain constraints? Process validation? Quality control?\n- What is the lead time for manufacturing equipment, tooling, or facility buildout?\n- At what volume does the manufacturing method break? When must a new method be adopted?\n- What manufacturing data does regulatory require? When can that validation begin?\n- What is the cost to scale from 1,000 units to 100,000 units? Does that change the business model?\n\n**Red flags:**\n- \"Prototype is hand-assembled; we'll figure out manufacturing later.\" (Manufacturing scale is a major bottleneck and often takes longer than expected.)\n- Single-source suppliers or critical supply chain dependencies with long lead times.\n- Manufacturing validation and regulatory sign-off are treated as separate activities (they are intertwined).\n- No manufacturing lead involved in commercialization strategy.\n\n### Market Timing\n\n**Questions to press:**\n- When does the market window open? Is there a competitive deadline?\n- How long is the market window open? What conditions would close it?\n- Do regulatory timelines align with market opportunity? (Often they don't.)\n- What is the customer's buying cycle? Procurement timeline? Budget cycle?\n- Are there seasonal or economic factors that make certain launch windows better than others?\n- What competitive products are in the pipeline, and when will they launch?\n\n**Red flags:**\n- \"The market is ready now.\" (But regulatory approval takes 18 months.)\n- Market opportunity assumed to last indefinitely (most windows have an expiration date).\n- No customer conversations about adoption timeline or procurement process.\n- Market forecast assumes rapid adoption without evidence of customer pull.\n\n### Legal and Liability Structure\n\n**Questions to press:**\n- What is the liability exposure? Product liability, clinical liability, IP liability?\n- What insurance will be required? How much does it cost? When must it be in place?\n- Are there IP landmines? Patent infringement risk? Trade secret exposure?\n- What is the optimal legal entity structure for commercialization? (Subsidiary, joint venture, licensing agreement?)\n- Are there regulatory bodies that will oversee post-market surveillance or adverse events?\n- What warranties and indemnities will customers require?\n\n**Red flags:**\n- No legal review of the technology or business model.\n- Assumption that \"we'll address liability in Year 2.\" (Insurance and structure must be in place before launch.)\n- Patent landscape not mapped; freedom-to-operate not validated.\n- Terms and liability structure treated as separate from product strategy.\n\n### Capital and Financial Risk\n\n**Questions to press:**\n- What is the total capital required to reach market entry? (Include regulatory, manufacturing, market development.)\n- At what milestone are additional capital raises needed?\n- What runway does the current capital provide?\n- Does the unit economics model hold at launch volume? At scale?\n- What is the break-even volume? When is cash flow positive?\n- Are there milestone-based funding sources (grants, partnerships) that could extend runway?\n\n**Red flags:**\n- \"We'll fund the rest through revenue.\" (Cash flow positive is not realistic until well after launch.)\n- No financial model beyond year 2.\n- Capital requirements wildly underestimated (almost always the case).\n- Financing plan assumes one capital raise; no Plan B if that round fails.\n\n## Bottleneck Identification\n\n**Method:** After mapping all domains, identify the constraint with the longest timeline or the most uncertainty. That constraint determines the overall commercialization timeline — everything else must wait for it.\n\n**Common bottlenecks:**\n- Regulatory approval (almost always): 12–36 months typical.\n- Manufacturing scale-up: 12–24 months from design to production-ready.\n- Market window closure: Competitive or economic factors force a launch deadline.\n- Capital availability: Funding delays or cost overruns delay downstream phases.\n- Clinical data generation: Phase I\u002FII\u002FIII trials add 3–10 years depending on indication.\n\n**Key insight:** The timeline is the maximum of all constraints, not the sum. If regulatory takes 24 months and manufacturing takes 6 months, the total is 24 months — but only if they can overlap. Often they cannot, and the timeline stretches further.\n\n## Hidden Dependencies\n\nEvery domain makes assumptions about what the other domains will deliver. These assumptions are fragile and often wrong.\n\n**Examples of hidden dependencies:**\n- Regulatory pathway assumes technical design is locked (but technical team says design will evolve).\n- Manufacturing assumes regulatory requirements are final (but regulatory often requires manufacturing changes late).\n- Market timing assumes regulatory approval by Q3 (but regulatory is reviewing in parallel and may delay).\n- Capital plan assumes manufacturing will be under budget (but scale-up always costs more than estimated).\n- Clinical trial assumes stable product design (but design often changes during trials).\n\n**Surface these assumptions explicitly and validate each one with the responsible domain owner before proceeding.**\n\n## Output\n\nDelivery a risk map with these sections:\n\n1. **Technical Feasibility:** Current state, critical unknowns in the critical path, lock-in risks.\n2. **Regulatory Pathway:** Classification, expected timeline, precedent (or lack thereof), data requirements.\n3. **Manufacturing Scale:** Current method, bottlenecks, timeline to scale, cost model.\n4. **Market Timing:** Window duration, competitive threats, customer buying cycle, seasonal factors.\n5. **Legal and Liability:** Liability exposure, IP landscape, entity structure, insurance requirements.\n6. **Capital Requirements:** Total capital, milestones, runway, break-even timeline.\n7. **Bottleneck:** Which domain determines the overall timeline.\n8. **Hidden Dependencies:** Assumptions each domain is making about the others; flag the fragile ones.\n9. **Missing Expertise:** What domains are under-represented on the current team?\n10. **Next Step:** What validation or decision must happen before the phased roadmap can be synthesized?\n",{"name":5,"description":7},"main","f0f0efe1d4c64b51a51f44427ad147750d29154e","agents\u002Fcommercialization-lead\u002Fskills\u002Fcommercialization-risk-classification","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus","www.cuteoctopus.site","https:\u002F\u002Fgithub.com\u002Fcwik-tech","2026-10-27 06:12:19",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add cwik-tech\u002Foctopus --skill commercialization-risk-classification",{"tool":37,"command":38},"bunx","bunx skills add cwik-tech\u002Foctopus --skill commercialization-risk-classification",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cwik-tech\u002Foctopus --skill commercialization-risk-classification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fcommercialization-lead\u002Fskills\u002Fcommercialization-risk-classification\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7F5MQVQ3CHGM77Q51M4B1AC","twenty-year-land-plan","Apply the Bren discipline of evaluating every land and development decision on a twenty-year horizon, with a comprehensive plan for how the land, the community, and the surrounding public infrastructure evolve together. Deals optimized for a five-year exit are structurally different from deals that compound across generations; insist on knowing which kind you are making. Use when evaluating land, entitlements, master-planned development, or phasing decisions, and when separating five-year exit deals from generational holds.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Ftwenty-year-land-plan\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7F5MGQ8JSV27SFDQVVGFQE3","thematic-gut-check","Apply the Gray discipline of identifying the structural theme behind every real estate deal, testing where that theme sits in its capital-flow lifecycle, and insisting that deals without a named theme — or deals late in a crowded theme — clear a higher bar. A mediocre deal in a strong theme usually beats a clever deal in a weak one. Use when naming the structural thesis behind a deal, judging whether that theme is early or crowded, and setting the bar the deal must clear.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fthematic-gut-check\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7F5M8V64Y0ZD8PTPWEJQXJ9","supply-pipeline-gut-check","Apply the Zell discipline of grounding every real estate thesis in the local supply pipeline. Demand counts over adjectives — units under construction, units permitted, units proposed — and convert them into a forward absorption schedule. A deal that ignores the pipeline is a bet on a market you have not actually studied. Use when validating a market thesis, forecasting absorption and rent growth, or counting units under construction, permitted, and proposed.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fsupply-pipeline-gut-check\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7F5M3J2Q146BJC13TD3YCXF","ruin-scenario-mapping","Apply the Taleb discipline of identifying, for every real estate deal, the specific chain of events that produces ruin — permanent, unrecoverable capital loss — and verifying that no single such chain has non-trivial probability. Deals with any plausible ruin path must be restructured or abandoned. Use when sizing leverage, testing refinancing, covenant, and liquidity risk, or checking whether any single failure chain can permanently wipe out the position.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fruin-scenario-mapping\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7F5KZDS0DYD172P6HS0WXEM","revenue-cost-architecture","Design a venture's revenue streams, pricing logic, cost structure, and unit economics so the business model has a coherent theory of value capture, not just value creation. Use after the value proposition and customer segment are set and before financial projections, when choosing a pricing model, calculating contribution margin or CAC payback, or checking whether the unit economics hold at scale.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Frevenue-cost-architecture\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7F5KP1CNQMYAVCDTV4EEW3J","replacement-cost-stress-test","Apply the Buffett discipline of pricing every real estate asset against the cost to rebuild it from scratch. The ratio of purchase price to replacement cost sets a ceiling on long-run downside: below replacement cost, new supply cannot profitably undercut you; at or above it, you are buying a liability disguised as an asset. Use when setting a purchase price, judging downside protection, or testing how exposed an asset is to newly built competing supply.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Freplacement-cost-stress-test\u002FSKILL.md",[],[]]