[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4SBP7DHF4F73DFC23KBEG":3,"skill-same:01M7F4SBP7DHF4F73DFC23KBEG":67},{"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},"01M7F4SBP7DHF4F73DFC23KBEG","argument-synthesis",null,"Protocols for constructing, challenging, and reconciling positions in strategic deliberations. Core skill for all consulting agents. Use when combining competing viewpoints into a supported conclusion.","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\u002Finnovator\u002Fskills\u002Fargument-synthesis\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: argument-synthesis\ndescription: Protocols for constructing, challenging, and reconciling positions in strategic deliberations. Core skill for all consulting agents. Use when combining competing viewpoints into a supported conclusion.\n---\n\n# Argument Synthesis\n\n## Argument Construction Protocol\n\nBuild a position in this sequence:\n\n1. **Claim**: State your position in one declarative sentence. Avoid hedging.\n2. **Evidence**: List 2–4 concrete, verifiable facts or data points that support the claim.\n3. **Reasoning**: Explain *how* the evidence supports the claim. Name the causal mechanism or logical bridge.\n4. **Implications**: What follows if this claim is true? What changes? (Surfaces stakes and decisions downstream.)\n\nExample: \"We should divest from this market because [claim]. The sales decline is 12% YoY, churn accelerated to 18%, and unit economics have turned negative [evidence]. This pattern signals structural misalignment between product and customer needs—not cyclical demand [reasoning]. If we don't exit, we'll spend 2 years and $5M trying to fix something fundamentally broken [implications].\"\n\nSee `templates\u002Fposition-statement.md` for structured output format.\n\n## Challenge Protocol\n\nBefore attacking a position, identify its actual strengths and weaknesses:\n\n1. **Steel-man first**: Restate the opposing argument in its strongest, most charitable form. Add premises they didn't mention but clearly rely on.\n2. **Locate the weak points**: Does the argument have logical gaps, unsupported leaps, missing evidence, or selection bias? Name them specifically.\n3. **Test assumptions**: What must be true for this argument to hold? Are those assumptions clearly stated and reasonable?\n4. **Check for bias**: See `references\u002Fcognitive-biases.md` for 10 common patterns. Does this argument show signs of anchoring, confirmation bias, or availability heuristic?\n5. **Propose the rebuttal**: If you disagree, either challenge the evidence, the causal reasoning, or the underlying assumption—not the person.\n\n## Reconciliation Protocol\n\nWhen two positions conflict, don't compromise (split the difference). Synthesize:\n\n1. **Name the tension**: \"The tension is between X (fast scaling captures market share) and Y (slow scaling preserves unit economics).\"\n2. **Identify what each side sees clearly**: Side A sees risk of competitor capture. Side B sees risk of cash depletion. Both are real.\n3. **Find the hidden third option**: Can you reframe the problem so both goals align? (E.g., \"What if we scale fast in high-margin segments while building profitability in core?\")\n4. **Test the synthesis**: Does it resolve both concerns or just defer the choice? A true synthesis strengthens both positions.\n\n## Evidence Standards\n\n**Strong evidence** in consulting:\n- Recent quantitative data (within 6 months unless trend is multi-year)\n- Direct observation or primary source, not secondhand interpretation\n- Explicitly bounded (e.g., \"in this segment\" not \"always\")\n- Tested against reasonable alternative explanations\n\n**Weak evidence**:\n- Anecdotes, single examples, or outlier cases presented as patterns\n- Data older than 12 months without trend context\n- Absence of evidence (\"We haven't seen X\") misrepresented as evidence of absence\n- Expert opinion without reasoning—replace with first principles\n\n## Tension Identification\n\nName productive disagreements this way: \"The tension between [position A] and [position B] is whether [the underlying question].\"\n\nExamples:\n- \"The tension is whether speed of market entry outweighs risk of unrefined product.\"\n- \"The tension is whether past success in similar pivots means this pivot will succeed, or whether each market is unique.\"\n\nThis framing prevents it becoming personal and keeps focus on the trade-off.\n\n## Concession Signals\n\nUpdate your position when:\n- New evidence contradicts a key assumption you didn't know was testable\n- A counter-argument exposes a logical gap you can't close\n- The opposing side steelman'd your position and it still holds, but reveals nuance you'd missed\n\nHold firm when:\n- The counter-argument relies on unsupported assumptions\n- New evidence is weaker than the foundation of your position\n- Conceding would require abandoning reasoning you still believe is sound\n\nSignal updates clearly: \"I didn't account for [X]. This shifts my confidence from 80% to 60% on [specific claim].\"\n\n## Red Team Protocol\n\nWhen a position or plan needs stress-testing beyond the Challenge Protocol, escalate to red teaming. The Challenge Protocol tests individual arguments; red teaming tests the **overall strategy or plan** for failure modes.\n\n1. **Assign the adversary role.** Explicitly shift from balanced analysis to active attack. Your job: make the plan fail.\n2. **Attack from six angles:** Market, execution, assumptions, timing, political, and black swan. See `references\u002Fred-teaming.md` for the full attack framework.\n3. **Document vulnerabilities** with attack vector, severity, probability, and mitigation.\n4. **Rank by severity × probability.** Present the top 3 critical findings.\n5. **Frame constructively:** \"This plan succeeds if [assumption]. Here's how to protect against [assumption] failing.\"\n\nUse red teaming when: evaluating a specific proposal, when the team is overconfident, or when stakeholders disagree on risks.\n\n## Pre-Mortem Protocol\n\nAfter developing a plan but before committing to execution, run a pre-mortem: assume the plan has already failed and work backward.\n\n1. **Set the frame:** \"It's 12 months from now. This plan failed. What went wrong?\"\n2. **Generate failure narratives** independently — don't anchor on one person's story.\n3. **Categorize by type:** Strategy, execution, external, internal, assumption failures.\n4. **Find convergence:** Multiple failure stories pointing to the same cause = high-confidence risk.\n5. **Convert to preventive actions:** Early warning signals, probability-reducing actions, contingency plans.\n\nSee `references\u002Fred-teaming.md` for the full protocol including when to use red teaming vs. pre-mortem.\n\n## References & Templates\n\n- `references\u002Fargumentation-frameworks.md` — Toulmin model, dialectical reasoning, Pyramid Principle\n- `references\u002Fcognitive-biases.md` — Detection and counters for 10 biases\n- `references\u002Fred-teaming.md` — Red team attack framework and pre-mortem protocol\n- `templates\u002Fposition-statement.md` — Structured format for stating positions\n","# Argument Synthesis\n\n## Argument Construction Protocol\n\nBuild a position in this sequence:\n\n1. **Claim**: State your position in one declarative sentence. Avoid hedging.\n2. **Evidence**: List 2–4 concrete, verifiable facts or data points that support the claim.\n3. **Reasoning**: Explain *how* the evidence supports the claim. Name the causal mechanism or logical bridge.\n4. **Implications**: What follows if this claim is true? What changes? (Surfaces stakes and decisions downstream.)\n\nExample: \"We should divest from this market because [claim]. The sales decline is 12% YoY, churn accelerated to 18%, and unit economics have turned negative [evidence]. This pattern signals structural misalignment between product and customer needs—not cyclical demand [reasoning]. If we don't exit, we'll spend 2 years and $5M trying to fix something fundamentally broken [implications].\"\n\nSee `templates\u002Fposition-statement.md` for structured output format.\n\n## Challenge Protocol\n\nBefore attacking a position, identify its actual strengths and weaknesses:\n\n1. **Steel-man first**: Restate the opposing argument in its strongest, most charitable form. Add premises they didn't mention but clearly rely on.\n2. **Locate the weak points**: Does the argument have logical gaps, unsupported leaps, missing evidence, or selection bias? Name them specifically.\n3. **Test assumptions**: What must be true for this argument to hold? Are those assumptions clearly stated and reasonable?\n4. **Check for bias**: See `references\u002Fcognitive-biases.md` for 10 common patterns. Does this argument show signs of anchoring, confirmation bias, or availability heuristic?\n5. **Propose the rebuttal**: If you disagree, either challenge the evidence, the causal reasoning, or the underlying assumption—not the person.\n\n## Reconciliation Protocol\n\nWhen two positions conflict, don't compromise (split the difference). Synthesize:\n\n1. **Name the tension**: \"The tension is between X (fast scaling captures market share) and Y (slow scaling preserves unit economics).\"\n2. **Identify what each side sees clearly**: Side A sees risk of competitor capture. Side B sees risk of cash depletion. Both are real.\n3. **Find the hidden third option**: Can you reframe the problem so both goals align? (E.g., \"What if we scale fast in high-margin segments while building profitability in core?\")\n4. **Test the synthesis**: Does it resolve both concerns or just defer the choice? A true synthesis strengthens both positions.\n\n## Evidence Standards\n\n**Strong evidence** in consulting:\n- Recent quantitative data (within 6 months unless trend is multi-year)\n- Direct observation or primary source, not secondhand interpretation\n- Explicitly bounded (e.g., \"in this segment\" not \"always\")\n- Tested against reasonable alternative explanations\n\n**Weak evidence**:\n- Anecdotes, single examples, or outlier cases presented as patterns\n- Data older than 12 months without trend context\n- Absence of evidence (\"We haven't seen X\") misrepresented as evidence of absence\n- Expert opinion without reasoning—replace with first principles\n\n## Tension Identification\n\nName productive disagreements this way: \"The tension between [position A] and [position B] is whether [the underlying question].\"\n\nExamples:\n- \"The tension is whether speed of market entry outweighs risk of unrefined product.\"\n- \"The tension is whether past success in similar pivots means this pivot will succeed, or whether each market is unique.\"\n\nThis framing prevents it becoming personal and keeps focus on the trade-off.\n\n## Concession Signals\n\nUpdate your position when:\n- New evidence contradicts a key assumption you didn't know was testable\n- A counter-argument exposes a logical gap you can't close\n- The opposing side steelman'd your position and it still holds, but reveals nuance you'd missed\n\nHold firm when:\n- The counter-argument relies on unsupported assumptions\n- New evidence is weaker than the foundation of your position\n- Conceding would require abandoning reasoning you still believe is sound\n\nSignal updates clearly: \"I didn't account for [X]. This shifts my confidence from 80% to 60% on [specific claim].\"\n\n## Red Team Protocol\n\nWhen a position or plan needs stress-testing beyond the Challenge Protocol, escalate to red teaming. The Challenge Protocol tests individual arguments; red teaming tests the **overall strategy or plan** for failure modes.\n\n1. **Assign the adversary role.** Explicitly shift from balanced analysis to active attack. Your job: make the plan fail.\n2. **Attack from six angles:** Market, execution, assumptions, timing, political, and black swan. See `references\u002Fred-teaming.md` for the full attack framework.\n3. **Document vulnerabilities** with attack vector, severity, probability, and mitigation.\n4. **Rank by severity × probability.** Present the top 3 critical findings.\n5. **Frame constructively:** \"This plan succeeds if [assumption]. Here's how to protect against [assumption] failing.\"\n\nUse red teaming when: evaluating a specific proposal, when the team is overconfident, or when stakeholders disagree on risks.\n\n## Pre-Mortem Protocol\n\nAfter developing a plan but before committing to execution, run a pre-mortem: assume the plan has already failed and work backward.\n\n1. **Set the frame:** \"It's 12 months from now. This plan failed. What went wrong?\"\n2. **Generate failure narratives** independently — don't anchor on one person's story.\n3. **Categorize by type:** Strategy, execution, external, internal, assumption failures.\n4. **Find convergence:** Multiple failure stories pointing to the same cause = high-confidence risk.\n5. **Convert to preventive actions:** Early warning signals, probability-reducing actions, contingency plans.\n\nSee `references\u002Fred-teaming.md` for the full protocol including when to use red teaming vs. pre-mortem.\n\n## References & Templates\n\n- `references\u002Fargumentation-frameworks.md` — Toulmin model, dialectical reasoning, Pyramid Principle\n- `references\u002Fcognitive-biases.md` — Detection and counters for 10 biases\n- `references\u002Fred-teaming.md` — Red team attack framework and pre-mortem protocol\n- `templates\u002Fposition-statement.md` — Structured format for stating positions\n",{"name":5,"description":7},"main","f0f0efe1d4c64b51a51f44427ad147750d29154e","agents\u002Finnovator\u002Fskills\u002Fargument-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 argument-synthesis",{"tool":37,"command":38},"bunx","bunx skills add cwik-tech\u002Foctopus --skill argument-synthesis",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cwik-tech\u002Foctopus --skill argument-synthesis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Finnovator\u002Fskills\u002Fargument-synthesis\u002FSKILL.md",true,[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Farchive\u002Fextended-biases.md","REFERENCE","参考文档",10175,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Finnovator\u002Fskills\u002Fargument-synthesis\u002Freferences\u002Farchive\u002Fextended-biases.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fargumentation-frameworks.md",4640,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Finnovator\u002Fskills\u002Fargument-synthesis\u002Freferences\u002Fargumentation-frameworks.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fcognitive-biases.md",5727,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Finnovator\u002Fskills\u002Fargument-synthesis\u002Freferences\u002Fcognitive-biases.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fred-teaming.md",4514,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Finnovator\u002Fskills\u002Fargument-synthesis\u002Freferences\u002Fred-teaming.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"templates\u002Fposition-statement.md",3454,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Finnovator\u002Fskills\u002Fargument-synthesis\u002Ftemplates\u002Fposition-statement.md",[68,75,82,89,96,103],{"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},"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":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},"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":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},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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",[],[]]