[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4VJC7E30HVRCEZEXR0DJW":3,"skill-same:01M7F4VJC7E30HVRCEZEXR0DJW":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},"01M7F4VJC7E30HVRCEZEXR0DJW","knowledge-project-orchestration",null,"Plan and orchestrate WP1–5 (Requirements, Parsing, Retrieval, Architecture, Pilot) sequencing, define gate criteria, manage dependencies, and ensure decision ownership","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\u002Fknowledge-product-architect\u002Fskills\u002Fknowledge-project-orchestration\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: knowledge-project-orchestration\ndescription: Plan and orchestrate WP1–5 (Requirements, Parsing, Retrieval, Architecture, Pilot) sequencing, define gate criteria, manage dependencies, and ensure decision ownership\n---\n\n# Knowledge Workpackage Orchestration\n\n## Purpose\n\nOrchestrate a knowledge systems project through five phases (WP1–5) from scope through pilot validation. Define the sequencing, gate criteria, and decision points. Ensure each phase produces the outputs required by the next phase and that no phase ships without evidence the gate criteria were met.\n\n## When to Use This Skill\n\n- **WP1 Planning:** At project start, define the five-phase roadmap, gate criteria for each phase, acceptance thresholds, and ownership.\n- **Phase Completion:** Before moving to the next phase, verify gate criteria were met; flag any blockers or evidence gaps.\n- **Risk Management:** Identify phase dependencies and critical path; escalate risks that could delay the overall roadmap.\n\n## Core Heuristics\n\n**The Gate Criterion:** Every phase must have a specific, measurable gate criterion before the next phase starts. \"Phase 2 is done\" is not a gate; \"Parsing fidelity on the test set is ≥90%\" is.\n\n**The Dependency Chain:**\n- WP1 output (pilot corpus, acceptance thresholds, build-vs-buy decision) gates WP2.\n- WP2 output (parser selection, fidelity results) gates WP3.\n- WP3 output (retrieval quality results, Recall@k ≥ threshold) gates WP4.\n- WP4 output (architecture, security review, cost model) gates WP5.\n- WP5 output (pilot validation, runbooks, handover readiness) unlocks scale-out.\n\nDo not parallelize phases unless dependencies allow (e.g., security threat modeling can start during WP1).\n\n**The Handover Criterion:** WP5 is not \"the pilot is done.\" It's \"the FST team can operate this knowledge base with documented runbooks and named ownership.\" If that's not true, the project isn't done.\n\n## Workflow\n\n1. **Define the five-phase roadmap:**\n   - WP1: Scope, inventory, acceptance criteria, build-vs-buy\n   - WP2: Parsing evaluation and selection\n   - WP3: Retrieval design and evaluation\n   - WP4: Architecture, security, cost model\n   - WP5: Pilot validation, runbooks, handover\n2. **Set gate criteria for each phase:**\n   - WP1 gate: Build-vs-buy documented and approved; pilot corpus defined; acceptance thresholds agreed\n   - WP2 gate: Parsing fidelity ≥ threshold on test set; parser selected\n   - WP3 gate: Retrieval Recall@k ≥ baseline + margin; citations verified; cost per query justified\n   - WP4 gate: Security review passed; architecture design approved; cost model validated; operational runbooks drafted\n   - WP5 gate: Acceptance criteria met; FST team trained and ready for handover; scale-out roadmap defined\n3. **Identify phase dependencies and critical path:**\n   - WP2 depends on WP1 (test corpus, fidelity threshold)\n   - WP3 depends on WP2 (parser output, chunking strategy)\n   - WP4 can start early (security threat modeling, landing zone design) but must complete before WP5\n   - WP5 depends on all prior phases\n4. **Manage risk and escalate blockers:**\n   - If a gate criterion cannot be met, escalate before the phase ends\n   - If a phase takes longer than planned, assess impact on downstream phases\n   - Keep a risk register (fidelity insufficient, access-control complexity, cost overrun, handover readiness)\n\n## Red Lines\n\n- Never move to the next phase without evidence the gate criteria were met\n- Never use \"we'll iterate in the next phase\" as an excuse to skip a gate\n- Never conflate \"the phase is done\" with \"we're ready to move on\"","# Knowledge Workpackage Orchestration\n\n## Purpose\n\nOrchestrate a knowledge systems project through five phases (WP1–5) from scope through pilot validation. Define the sequencing, gate criteria, and decision points. Ensure each phase produces the outputs required by the next phase and that no phase ships without evidence the gate criteria were met.\n\n## When to Use This Skill\n\n- **WP1 Planning:** At project start, define the five-phase roadmap, gate criteria for each phase, acceptance thresholds, and ownership.\n- **Phase Completion:** Before moving to the next phase, verify gate criteria were met; flag any blockers or evidence gaps.\n- **Risk Management:** Identify phase dependencies and critical path; escalate risks that could delay the overall roadmap.\n\n## Core Heuristics\n\n**The Gate Criterion:** Every phase must have a specific, measurable gate criterion before the next phase starts. \"Phase 2 is done\" is not a gate; \"Parsing fidelity on the test set is ≥90%\" is.\n\n**The Dependency Chain:**\n- WP1 output (pilot corpus, acceptance thresholds, build-vs-buy decision) gates WP2.\n- WP2 output (parser selection, fidelity results) gates WP3.\n- WP3 output (retrieval quality results, Recall@k ≥ threshold) gates WP4.\n- WP4 output (architecture, security review, cost model) gates WP5.\n- WP5 output (pilot validation, runbooks, handover readiness) unlocks scale-out.\n\nDo not parallelize phases unless dependencies allow (e.g., security threat modeling can start during WP1).\n\n**The Handover Criterion:** WP5 is not \"the pilot is done.\" It's \"the FST team can operate this knowledge base with documented runbooks and named ownership.\" If that's not true, the project isn't done.\n\n## Workflow\n\n1. **Define the five-phase roadmap:**\n   - WP1: Scope, inventory, acceptance criteria, build-vs-buy\n   - WP2: Parsing evaluation and selection\n   - WP3: Retrieval design and evaluation\n   - WP4: Architecture, security, cost model\n   - WP5: Pilot validation, runbooks, handover\n2. **Set gate criteria for each phase:**\n   - WP1 gate: Build-vs-buy documented and approved; pilot corpus defined; acceptance thresholds agreed\n   - WP2 gate: Parsing fidelity ≥ threshold on test set; parser selected\n   - WP3 gate: Retrieval Recall@k ≥ baseline + margin; citations verified; cost per query justified\n   - WP4 gate: Security review passed; architecture design approved; cost model validated; operational runbooks drafted\n   - WP5 gate: Acceptance criteria met; FST team trained and ready for handover; scale-out roadmap defined\n3. **Identify phase dependencies and critical path:**\n   - WP2 depends on WP1 (test corpus, fidelity threshold)\n   - WP3 depends on WP2 (parser output, chunking strategy)\n   - WP4 can start early (security threat modeling, landing zone design) but must complete before WP5\n   - WP5 depends on all prior phases\n4. **Manage risk and escalate blockers:**\n   - If a gate criterion cannot be met, escalate before the phase ends\n   - If a phase takes longer than planned, assess impact on downstream phases\n   - Keep a risk register (fidelity insufficient, access-control complexity, cost overrun, handover readiness)\n\n## Red Lines\n\n- Never move to the next phase without evidence the gate criteria were met\n- Never use \"we'll iterate in the next phase\" as an excuse to skip a gate\n- Never conflate \"the phase is done\" with \"we're ready to move on\"",{"name":5,"description":7},"main","f0f0efe1d4c64b51a51f44427ad147750d29154e","agents\u002Fknowledge-product-architect\u002Fskills\u002Fknowledge-project-orchestration","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 knowledge-project-orchestration",{"tool":37,"command":38},"bunx","bunx skills add cwik-tech\u002Foctopus --skill knowledge-project-orchestration",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cwik-tech\u002Foctopus --skill knowledge-project-orchestration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fknowledge-product-architect\u002Fskills\u002Fknowledge-project-orchestration\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",[],[]]