[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F48FE37RSVCZ4EX99HGKSV":3,"skill-same:01M7F48FE37RSVCZ4EX99HGKSV":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},"01M7F48FE37RSVCZ4EX99HGKSV","commercialization-roadmap-synthesis",null,"Synthesizes a phased commercialization roadmap from prototype to market entry with explicit gates, dependencies, and decision points. Identifies which activities can overlap, which must sequence, and what must be validated before each phase. Use after risk classification and specialist input have been gathered, when converting a risk map into a concrete timeline.","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-roadmap-synthesis\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: commercialization-roadmap-synthesis\ndescription: Synthesizes a phased commercialization roadmap from prototype to market entry with explicit gates, dependencies, and decision points. Identifies which activities can overlap, which must sequence, and what must be validated before each phase. Use after risk classification and specialist input have been gathered, when converting a risk map into a concrete timeline.\n---\n\n# Commercialization Roadmap Synthesis\n\n## Purpose\n\nConvert the risk landscape into a phased roadmap with explicit gates, dependencies, and decision points. Make clear which activities can run in parallel, which must sequence, and what must be true before the next phase begins.\n\n## When to Use\n\nUse this skill when:\n- All domain specialists have input on their risks and timelines.\n- The risk map has been validated and hidden dependencies surfaced.\n- A phased roadmap is needed to align the team and investors.\n- Timeline decisions must be made (e.g., \"Do we wait for regulatory decision before manufacturing scale-up?\").\n\n## Roadmap Structure\n\n### Phase Definitions\n\n**Phase 0 (Pre-Development):** Prototype exists, basic feasibility proven, but significant work remains.\n- Activities: Technical de-risking, preliminary regulatory research, manufacturing feasibility study, market sizing.\n- Gate: Technical design path clear, regulatory pathway identified, manufacturing method chosen.\n\n**Phase 1 (Regulatory Pathway):** Regulatory engagement and data generation begin.\n- Activities: Regulatory dossier preparation, clinical trial design\u002Finitiation, manufacturing data generation, supply chain development.\n- Gate: Regulatory submission filed, manufacturing pilot run successful, supply chain locked in.\n\n**Phase 2 (Regulatory Approval & Manufacturing Scale):** Parallel execution of approval and scale-up.\n- Activities: Regulatory review, clinical trial completion, manufacturing process validation, quality system buildout, commercial team assembly.\n- Gate: Regulatory approval received, manufacturing validated, commercial readiness confirmed.\n\n**Phase 3 (Market Entry & Scale):** Product launches, volume ramps, market development.\n- Activities: Market distribution, customer acquisition, manufacturing scale, post-market surveillance.\n- Gate: First revenue, market feedback incorporation, scale production achieved.\n\n### Gate Definitions\n\nEvery phase ends with a decision gate. A gate is a clear, testable requirement that must be met before the next phase begins.\n\n**Gate = (What must be true) + (Who decides) + (When does the decision happen)**\n\nExamples:\n- \"Regulatory pathway classification confirmed by [regulatory lead], by [date].\" (Clear and testable.)\n- \"Manufacturing pilot run achieves 80% yield at [volume], by [date].\" (Testable, not vague.)\n- \"Customers commit to [N] orders in first year, by [date].\" (Proves market demand.)\n\n**Red flags:**\n- \"We'll be ready when we're ready.\" (Not a gate — too vague.)\n- \"Regulatory approval.\" (A gate, but missing the owner and date.)\n- Gates that assume other gates are already met (use explicit dependencies instead).\n\n### Activity Sequencing\n\n**Activities that must sequence (one after the other):**\n- Technical design → Manufacturing design → Process validation (cannot parallelize)\n- Regulatory submission → Regulatory review → Regulatory approval (fixed order)\n- Clinical trial initiation → Trial enrollment → Trial completion → Data analysis (phases have dependencies)\n\n**Activities that can overlap (run in parallel):**\n- Technical design ↔ Preliminary regulatory research (inform each other but don't block)\n- Manufacturing scale-up ↔ Regulatory review (often independent streams)\n- Market development ↔ Regulatory approval (can start customer conversations in parallel)\n- Supply chain lock-in ↔ Manufacturing validation (can proceed in parallel)\n\n**Key insight:** Compress the timeline by running parallel activities wherever possible, but only if the activities truly do not block each other. Regulatory pathway almost always blocks manufacturing scale decisions — do not assume they can run fully in parallel.\n\n### Dependencies Across Domains\n\nMake all cross-domain dependencies explicit.\n\n**Examples:**\n- Regulatory pathway depends on: Technical design locked → use this to determine when regulatory engagement can start.\n- Manufacturing scale depends on: Regulatory pathway confirmed → know which manufacturing data regulatory requires before designing the process.\n- Market entry depends on: Regulatory approval + Manufacturing validation + Commercial team ready → all three must be true before launch date.\n\n## Timeline Construction\n\n### Method\n\n1. **List all activities** required from current state to market entry.\n2. **Assign ownership** to each activity (technical lead, regulatory lead, etc.).\n3. **Estimate duration** for each activity (ask the domain owner, do not guess).\n4. **Identify dependencies** (what activity must finish before this one starts?).\n5. **Build a Gantt chart mentally or visually:**\n   - Critical path activities: tasks whose delay delays the entire timeline.\n   - Non-critical activities: tasks with float (can slip a bit without impacting overall timeline).\n6. **Identify the bottleneck:** The critical path activity with the longest duration or highest risk.\n\n### Realistic Estimation\n\n**Common mistakes:**\n- Assuming activities start the moment they theoretically can (not accounting for resource availability or decision lag).\n- Underestimating regulatory and manufacturing timelines (almost always happens).\n- Assuming parallel activities share no resources (they do; resource contention adds delays).\n- Forgetting buffer time (add 20–30% buffer for delays, approvals, rework).\n\n**Recommendations:**\n- Ask domain experts for estimates, not guesses.\n- Add precedent-based estimates (\"How long did regulatory take for Product X?\")\n- Identify high-risk activities and add extra buffer (regulatory decisions, clinical trials, supply chain).\n- Use a pessimistic estimate for the critical path; use a realistic estimate for non-critical work.\n\n## Phased Roadmap Output\n\nDelivery a roadmap with these components:\n\n### Phase [N] Timeline\n- **Duration:** [Start date] to [End date] ([X months])\n- **Gate:** [Clear, testable requirement that must be met to proceed]\n- **Activities:**\n  - [Activity name] (Owner: [name], Duration: [X weeks\u002Fmonths])\n  - [Dependency information if relevant]\n- **Critical Assumptions:** [Key assumptions that, if wrong, derail this phase]\n- **Risk Highlights:** [Highest-risk activities in this phase]\n\n### Phase Summary Table\n\n| Phase | Duration | Owner | Gate | Risk |\n|-------|----------|-------|------|------|\n| ... | ... | ... | ... | ... |\n\n### Critical Path\n\nIdentify the sequence of activities that determines the overall timeline. Any delay in a critical-path activity delays the launch date.\n\n**Format:**\n- Activity A (X months) → Activity B (Y months) → Activity C (Z months) = Total of (X+Y+Z) months\n- Non-critical activity D (can slip X weeks without impacting launch)\n\n### Decision Gates and Owners\n\nEvery gate must have a named owner and a decision date. No orphaned gates.\n\n**Format:**\n- Gate: [What must be true]\n- Owner: [Name\u002Frole]\n- Decision date: [Date]\n- If gate is not met by decision date: [What happens? Do we pivot, delay, or accept risk?]\n\n### Hidden Risks and Assumptions\n\nList assumptions that, if wrong, would force a timeline re-plan:\n- Assumption: \"Regulatory pathway is Class II.\"\n  - If wrong: Reclassified as Class III → add 12–18 months for clinical data.\n- Assumption: \"Manufacturing scale will be ready by Q3.\"\n  - If wrong: Supplier delays → delay Phase 2 by 6 months.\n\n## Next Action\n\nOnce the roadmap is synthesized:\n\n1. **Socialize with specialists:** Walk each domain lead through the roadmap. Validate dependencies and timelines.\n2. **Identify owners:** Every gate and critical activity must have a named owner.\n3. **Add contingency plans:** For each high-risk activity, define Plan B if it slips or fails.\n4. **Lock funding:** Ensure capital is available at each funding gate.\n5. **Set decision dates:** Calendar all gates and decisions. Do not allow them to drift.\n","# Commercialization Roadmap Synthesis\n\n## Purpose\n\nConvert the risk landscape into a phased roadmap with explicit gates, dependencies, and decision points. Make clear which activities can run in parallel, which must sequence, and what must be true before the next phase begins.\n\n## When to Use\n\nUse this skill when:\n- All domain specialists have input on their risks and timelines.\n- The risk map has been validated and hidden dependencies surfaced.\n- A phased roadmap is needed to align the team and investors.\n- Timeline decisions must be made (e.g., \"Do we wait for regulatory decision before manufacturing scale-up?\").\n\n## Roadmap Structure\n\n### Phase Definitions\n\n**Phase 0 (Pre-Development):** Prototype exists, basic feasibility proven, but significant work remains.\n- Activities: Technical de-risking, preliminary regulatory research, manufacturing feasibility study, market sizing.\n- Gate: Technical design path clear, regulatory pathway identified, manufacturing method chosen.\n\n**Phase 1 (Regulatory Pathway):** Regulatory engagement and data generation begin.\n- Activities: Regulatory dossier preparation, clinical trial design\u002Finitiation, manufacturing data generation, supply chain development.\n- Gate: Regulatory submission filed, manufacturing pilot run successful, supply chain locked in.\n\n**Phase 2 (Regulatory Approval & Manufacturing Scale):** Parallel execution of approval and scale-up.\n- Activities: Regulatory review, clinical trial completion, manufacturing process validation, quality system buildout, commercial team assembly.\n- Gate: Regulatory approval received, manufacturing validated, commercial readiness confirmed.\n\n**Phase 3 (Market Entry & Scale):** Product launches, volume ramps, market development.\n- Activities: Market distribution, customer acquisition, manufacturing scale, post-market surveillance.\n- Gate: First revenue, market feedback incorporation, scale production achieved.\n\n### Gate Definitions\n\nEvery phase ends with a decision gate. A gate is a clear, testable requirement that must be met before the next phase begins.\n\n**Gate = (What must be true) + (Who decides) + (When does the decision happen)**\n\nExamples:\n- \"Regulatory pathway classification confirmed by [regulatory lead], by [date].\" (Clear and testable.)\n- \"Manufacturing pilot run achieves 80% yield at [volume], by [date].\" (Testable, not vague.)\n- \"Customers commit to [N] orders in first year, by [date].\" (Proves market demand.)\n\n**Red flags:**\n- \"We'll be ready when we're ready.\" (Not a gate — too vague.)\n- \"Regulatory approval.\" (A gate, but missing the owner and date.)\n- Gates that assume other gates are already met (use explicit dependencies instead).\n\n### Activity Sequencing\n\n**Activities that must sequence (one after the other):**\n- Technical design → Manufacturing design → Process validation (cannot parallelize)\n- Regulatory submission → Regulatory review → Regulatory approval (fixed order)\n- Clinical trial initiation → Trial enrollment → Trial completion → Data analysis (phases have dependencies)\n\n**Activities that can overlap (run in parallel):**\n- Technical design ↔ Preliminary regulatory research (inform each other but don't block)\n- Manufacturing scale-up ↔ Regulatory review (often independent streams)\n- Market development ↔ Regulatory approval (can start customer conversations in parallel)\n- Supply chain lock-in ↔ Manufacturing validation (can proceed in parallel)\n\n**Key insight:** Compress the timeline by running parallel activities wherever possible, but only if the activities truly do not block each other. Regulatory pathway almost always blocks manufacturing scale decisions — do not assume they can run fully in parallel.\n\n### Dependencies Across Domains\n\nMake all cross-domain dependencies explicit.\n\n**Examples:**\n- Regulatory pathway depends on: Technical design locked → use this to determine when regulatory engagement can start.\n- Manufacturing scale depends on: Regulatory pathway confirmed → know which manufacturing data regulatory requires before designing the process.\n- Market entry depends on: Regulatory approval + Manufacturing validation + Commercial team ready → all three must be true before launch date.\n\n## Timeline Construction\n\n### Method\n\n1. **List all activities** required from current state to market entry.\n2. **Assign ownership** to each activity (technical lead, regulatory lead, etc.).\n3. **Estimate duration** for each activity (ask the domain owner, do not guess).\n4. **Identify dependencies** (what activity must finish before this one starts?).\n5. **Build a Gantt chart mentally or visually:**\n   - Critical path activities: tasks whose delay delays the entire timeline.\n   - Non-critical activities: tasks with float (can slip a bit without impacting overall timeline).\n6. **Identify the bottleneck:** The critical path activity with the longest duration or highest risk.\n\n### Realistic Estimation\n\n**Common mistakes:**\n- Assuming activities start the moment they theoretically can (not accounting for resource availability or decision lag).\n- Underestimating regulatory and manufacturing timelines (almost always happens).\n- Assuming parallel activities share no resources (they do; resource contention adds delays).\n- Forgetting buffer time (add 20–30% buffer for delays, approvals, rework).\n\n**Recommendations:**\n- Ask domain experts for estimates, not guesses.\n- Add precedent-based estimates (\"How long did regulatory take for Product X?\")\n- Identify high-risk activities and add extra buffer (regulatory decisions, clinical trials, supply chain).\n- Use a pessimistic estimate for the critical path; use a realistic estimate for non-critical work.\n\n## Phased Roadmap Output\n\nDelivery a roadmap with these components:\n\n### Phase [N] Timeline\n- **Duration:** [Start date] to [End date] ([X months])\n- **Gate:** [Clear, testable requirement that must be met to proceed]\n- **Activities:**\n  - [Activity name] (Owner: [name], Duration: [X weeks\u002Fmonths])\n  - [Dependency information if relevant]\n- **Critical Assumptions:** [Key assumptions that, if wrong, derail this phase]\n- **Risk Highlights:** [Highest-risk activities in this phase]\n\n### Phase Summary Table\n\n| Phase | Duration | Owner | Gate | Risk |\n|-------|----------|-------|------|------|\n| ... | ... | ... | ... | ... |\n\n### Critical Path\n\nIdentify the sequence of activities that determines the overall timeline. Any delay in a critical-path activity delays the launch date.\n\n**Format:**\n- Activity A (X months) → Activity B (Y months) → Activity C (Z months) = Total of (X+Y+Z) months\n- Non-critical activity D (can slip X weeks without impacting launch)\n\n### Decision Gates and Owners\n\nEvery gate must have a named owner and a decision date. No orphaned gates.\n\n**Format:**\n- Gate: [What must be true]\n- Owner: [Name\u002Frole]\n- Decision date: [Date]\n- If gate is not met by decision date: [What happens? Do we pivot, delay, or accept risk?]\n\n### Hidden Risks and Assumptions\n\nList assumptions that, if wrong, would force a timeline re-plan:\n- Assumption: \"Regulatory pathway is Class II.\"\n  - If wrong: Reclassified as Class III → add 12–18 months for clinical data.\n- Assumption: \"Manufacturing scale will be ready by Q3.\"\n  - If wrong: Supplier delays → delay Phase 2 by 6 months.\n\n## Next Action\n\nOnce the roadmap is synthesized:\n\n1. **Socialize with specialists:** Walk each domain lead through the roadmap. Validate dependencies and timelines.\n2. **Identify owners:** Every gate and critical activity must have a named owner.\n3. **Add contingency plans:** For each high-risk activity, define Plan B if it slips or fails.\n4. **Lock funding:** Ensure capital is available at each funding gate.\n5. **Set decision dates:** Calendar all gates and decisions. Do not allow them to drift.\n",{"name":5,"description":7},"main","f0f0efe1d4c64b51a51f44427ad147750d29154e","agents\u002Fcommercialization-lead\u002Fskills\u002Fcommercialization-roadmap-synthesis","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-roadmap-synthesis",{"tool":37,"command":38},"bunx","bunx skills add cwik-tech\u002Foctopus --skill commercialization-roadmap-synthesis",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cwik-tech\u002Foctopus --skill commercialization-roadmap-synthesis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fcommercialization-lead\u002Fskills\u002Fcommercialization-roadmap-synthesis\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",[],[]]