[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P3K74RECFJHBP69VPDBCW":3,"skill-same:01M71P3K74RECFJHBP69VPDBCW":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M71P3K74RECFJHBP69VPDBCW","startup-financial-modeling",null,"Use when building a 3-5 year startup financial model: cohort revenue, cost structure, cash flow, burn, runway and seed or Series A fundraising scenarios. For tracking and benchmarking operating metrics like CAC and LTV see startup-metrics-framework.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstartup-financial-modeling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstartup-financial-modeling\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"modeling","financial modeling","startup","startup financial modeling","planning","fundraising","framework","metrics","flow","seed","financial-modeling","cost structure","analyst","revenue","runway","benchmarking","structure","when","model","operating","2026-11-10 10:56:23",false,"---\nname: startup-financial-modeling\ndescription: \"Use when building a 3-5 year startup financial model: cohort revenue, cost structure, cash flow, burn, runway and seed or Series A fundraising scenarios. For tracking and benchmarking operating metrics like CAC and LTV see startup-metrics-framework.\"\ntags: [\"finance\",\"fundraising\",\"planning\"]\ntools: []\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Fwshobson\u002Fagents\nsource_path: \"plugins\u002Fstartup-business-analyst\u002Fskills\u002Fstartup-financial-modeling\"\nsource_commit: 4236bb91f8395b0435f1d8b8baf9e8e4c69a8620\n---\n# Startup Financial Modeling\n\nBuild comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.\n\n## Overview\n\nFinancial modeling provides the quantitative foundation for startup strategy, fundraising, and operational planning. Create realistic projections using cohort-based revenue modeling, detailed cost structures, and scenario analysis to support decision-making and investor presentations.\n\n## Core Components\n\n### Revenue Model\n\n**Cohort-Based Projections:**\nBuild revenue from customer acquisition and retention by cohort.\n\n**Formula:**\n\n```\nMRR = Σ (Cohort Size × Retention Rate × ARPU)\nARR = MRR × 12\n```\n\n**Key Inputs:**\n\n- Monthly new customer acquisitions\n- Customer retention rates by month\n- Average revenue per user (ARPU)\n- Pricing and packaging assumptions\n- Expansion revenue (upsells, cross-sells)\n\n### Cost Structure\n\n**Operating Expenses Categories:**\n\n1. **Cost of Goods Sold (COGS)**\n   - Hosting and infrastructure\n   - Payment processing fees\n   - Customer support (variable portion)\n   - Third-party services per customer\n\n2. **Sales & Marketing (S&M)**\n   - Customer acquisition cost (CAC)\n   - Marketing programs and advertising\n   - Sales team compensation\n   - Marketing tools and software\n\n3. **Research & Development (R&D)**\n   - Engineering team compensation\n   - Product management\n   - Design and UX\n   - Development tools and infrastructure\n\n4. **General & Administrative (G&A)**\n   - Executive team\n   - Finance, legal, HR\n   - Office and facilities\n   - Insurance and compliance\n\n### Cash Flow Analysis\n\n**Components:**\n\n- Beginning cash balance\n- Cash inflows (revenue, fundraising)\n- Cash outflows (operating expenses, CapEx)\n- Ending cash balance\n- Monthly burn rate\n- Runway (months of cash remaining)\n\n**Formula:**\n\n```\nRunway = Current Cash Balance \u002F Monthly Burn Rate\nMonthly Burn = Monthly Revenue - Monthly Expenses\n```\n\n### Headcount Planning\n\n**Role-Based Hiring Plan:**\nTrack headcount by department and role.\n\n**Key Metrics:**\n\n- Fully-loaded cost per employee\n- Revenue per employee\n- Headcount by department (% of total)\n\n**Typical Ratios (Early-Stage SaaS):**\n\n- Engineering: 40-50%\n- Sales & Marketing: 25-35%\n- G&A: 10-15%\n- Customer Success: 5-10%\n\n## Financial Model Structure\n\n### Three-Scenario Framework\n\n**Conservative Scenario (P10):**\n\n- Slower customer acquisition\n- Lower pricing or conversion\n- Higher churn rates\n- Extended sales cycles\n- Used for cash management\n\n**Base Scenario (P50):**\n\n- Most likely outcomes\n- Realistic assumptions\n- Primary planning scenario\n- Used for board reporting\n\n**Optimistic Scenario (P90):**\n\n- Faster growth\n- Better unit economics\n- Lower churn\n- Used for upside planning\n\n### Time Horizon\n\n**Detailed Projections: 3 Years**\n\n- Monthly detail for Year 1\n- Monthly detail for Year 2\n- Quarterly detail for Year 3\n\n**High-Level Projections: Years 4-5**\n\n- Annual projections\n- Key metrics only\n- Support long-term planning\n\n## Detailed section: Step-by-Step Process\n\nOriginally a 2763-byte section in this SKILL.md. Moved to `references\u002Fdetails.md` to fit Codex's 8 KB skill body cap.\n\n## Business Model Templates\n\n### SaaS Financial Model\n\n**Revenue Drivers:**\n\n- New MRR (customers × ARPU)\n- Expansion MRR (upsells)\n- Contraction MRR (downgrades)\n- Churned MRR (lost customers)\n\n**Key Ratios:**\n\n- Gross margin: 75-85%\n- S&M as % revenue: 40-60% (early stage)\n- CAC payback: \u003C 12 months\n- Net retention: 100-120%\n\n**Example Projection:**\n\n```\nYear 1: $500K ARR, 50 customers, $100K MRR by Dec\nYear 2: $2.5M ARR, 200 customers, $208K MRR by Dec\nYear 3: $8M ARR, 600 customers, $667K MRR by Dec\n```\n\n### Marketplace Financial Model\n\n**Revenue Drivers:**\n\n- GMV (Gross Merchandise Value)\n- Take rate (% of GMV)\n- Net revenue = GMV × Take rate\n\n**Key Ratios:**\n\n- Take rate: 10-30% depending on category\n- CAC for buyers vs. sellers\n- Contribution margin: 60-70%\n\n**Example Projection:**\n\n```\nYear 1: $5M GMV, 15% take rate = $750K revenue\nYear 2: $20M GMV, 15% take rate = $3M revenue\nYear 3: $60M GMV, 15% take rate = $9M revenue\n```\n\n### E-Commerce Financial Model\n\n**Revenue Drivers:**\n\n- Traffic (visitors)\n- Conversion rate\n- Average order value (AOV)\n- Purchase frequency\n\n**Key Ratios:**\n\n- Gross margin: 40-60%\n- Contribution margin: 20-35%\n- CAC payback: 3-6 months\n\n### Services \u002F Agency Financial Model\n\n**Revenue Drivers:**\n\n- Billable hours or projects\n- Hourly rate or project fee\n- Utilization rate\n- Team capacity\n\n**Key Ratios:**\n\n- Gross margin: 50-70%\n- Utilization: 70-85%\n- Revenue per employee\n\n## Fundraising Integration\n\n### Funding Scenario Modeling\n\n**Pre-Money Valuation:**\nBased on metrics and comparables.\n\n**Dilution:**\n\n```\nPost-Money = Pre-Money + Investment\nDilution % = Investment \u002F Post-Money\n```\n\n**Use of Funds:**\nAllocate funding to extend runway and achieve milestones.\n\n**Example:**\n\n```\nRaise: $5M at $20M pre-money\nPost-Money: $25M\nDilution: 20%\n\nUse of Funds:\n- Product Development: $2M (40%)\n- Sales & Marketing: $2M (40%)\n- G&A and Operations: $0.5M (10%)\n- Working Capital: $0.5M (10%)\n```\n\n### Milestone-Based Planning\n\n**Identify Key Milestones:**\n\n- Product launch\n- First $1M ARR\n- Break-even on CAC\n- Series A fundraise\n\n**Funding Amount:**\nEnsure runway to achieve next milestone + 6 months buffer.\n\n## Common Pitfalls\n\n**Pitfall 1: Overly Optimistic Revenue**\n\n- New startups rarely hit aggressive projections\n- Use conservative customer acquisition assumptions\n- Model realistic churn rates\n\n**Pitfall 2: Underestimating Costs**\n\n- Add 20% buffer to expense estimates\n- Include fully-loaded compensation\n- Account for software and tools\n\n**Pitfall 3: Ignoring Cash Flow Timing**\n\n- Revenue ≠ cash (payment terms)\n- Expenses paid before revenue collected\n- Model cash conversion carefully\n\n**Pitfall 4: Static Headcount**\n\n- Hiring takes time (3-6 months to fill roles)\n- Ramp time for productivity (3-6 months)\n- Account for attrition (10-15% annually)\n\n**Pitfall 5: Not Scenario Planning**\n\n- Single scenario is never accurate\n- Always model conservative case\n- Plan for what you'll do if base case fails\n\n## Model Validation\n\n**Sanity Checks:**\n\n- [ ] Revenue growth rate is achievable (3x in Year 2, 2x in Year 3)\n- [ ] Unit economics are realistic (LTV\u002FCAC > 3, payback \u003C 18 months)\n- [ ] Burn multiple is reasonable (\u003C 2.0 in Year 2-3)\n- [ ] Headcount scales with revenue (revenue per employee growing)\n- [ ] Gross margin is appropriate for business model\n- [ ] S&M spending aligns with CAC and growth targets\n\n**Benchmark Against Peers:**\nCompare key metrics to similar companies at similar stage.\n\n**Investor Feedback:**\nShare model with advisors or investors for feedback on assumptions.\n\n\n## Quick Start\n\nTo create a startup financial model:\n\n1. **Define business model** - Revenue drivers and pricing\n2. **Project revenue** - Cohort-based with retention\n3. **Model costs** - COGS, S&M, R&D, G&A by month\n4. **Plan headcount** - Hiring by role and department\n5. **Calculate cash flow** - Revenue - expenses = burn\u002Frunway\n6. **Compute metrics** - CAC, LTV, burn multiple, runway\n7. **Create scenarios** - Conservative, base, optimistic\n8. **Validate assumptions** - Sanity check and benchmark\n9. **Integrate fundraising** - Model funding rounds and milestones\n","# Startup Financial Modeling\n\nBuild comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.\n\n## Overview\n\nFinancial modeling provides the quantitative foundation for startup strategy, fundraising, and operational planning. Create realistic projections using cohort-based revenue modeling, detailed cost structures, and scenario analysis to support decision-making and investor presentations.\n\n## Core Components\n\n### Revenue Model\n\n**Cohort-Based Projections:**\nBuild revenue from customer acquisition and retention by cohort.\n\n**Formula:**\n\n```\nMRR = Σ (Cohort Size × Retention Rate × ARPU)\nARR = MRR × 12\n```\n\n**Key Inputs:**\n\n- Monthly new customer acquisitions\n- Customer retention rates by month\n- Average revenue per user (ARPU)\n- Pricing and packaging assumptions\n- Expansion revenue (upsells, cross-sells)\n\n### Cost Structure\n\n**Operating Expenses Categories:**\n\n1. **Cost of Goods Sold (COGS)**\n   - Hosting and infrastructure\n   - Payment processing fees\n   - Customer support (variable portion)\n   - Third-party services per customer\n\n2. **Sales & Marketing (S&M)**\n   - Customer acquisition cost (CAC)\n   - Marketing programs and advertising\n   - Sales team compensation\n   - Marketing tools and software\n\n3. **Research & Development (R&D)**\n   - Engineering team compensation\n   - Product management\n   - Design and UX\n   - Development tools and infrastructure\n\n4. **General & Administrative (G&A)**\n   - Executive team\n   - Finance, legal, HR\n   - Office and facilities\n   - Insurance and compliance\n\n### Cash Flow Analysis\n\n**Components:**\n\n- Beginning cash balance\n- Cash inflows (revenue, fundraising)\n- Cash outflows (operating expenses, CapEx)\n- Ending cash balance\n- Monthly burn rate\n- Runway (months of cash remaining)\n\n**Formula:**\n\n```\nRunway = Current Cash Balance \u002F Monthly Burn Rate\nMonthly Burn = Monthly Revenue - Monthly Expenses\n```\n\n### Headcount Planning\n\n**Role-Based Hiring Plan:**\nTrack headcount by department and role.\n\n**Key Metrics:**\n\n- Fully-loaded cost per employee\n- Revenue per employee\n- Headcount by department (% of total)\n\n**Typical Ratios (Early-Stage SaaS):**\n\n- Engineering: 40-50%\n- Sales & Marketing: 25-35%\n- G&A: 10-15%\n- Customer Success: 5-10%\n\n## Financial Model Structure\n\n### Three-Scenario Framework\n\n**Conservative Scenario (P10):**\n\n- Slower customer acquisition\n- Lower pricing or conversion\n- Higher churn rates\n- Extended sales cycles\n- Used for cash management\n\n**Base Scenario (P50):**\n\n- Most likely outcomes\n- Realistic assumptions\n- Primary planning scenario\n- Used for board reporting\n\n**Optimistic Scenario (P90):**\n\n- Faster growth\n- Better unit economics\n- Lower churn\n- Used for upside planning\n\n### Time Horizon\n\n**Detailed Projections: 3 Years**\n\n- Monthly detail for Year 1\n- Monthly detail for Year 2\n- Quarterly detail for Year 3\n\n**High-Level Projections: Years 4-5**\n\n- Annual projections\n- Key metrics only\n- Support long-term planning\n\n## Detailed section: Step-by-Step Process\n\nOriginally a 2763-byte section in this SKILL.md. Moved to `references\u002Fdetails.md` to fit Codex's 8 KB skill body cap.\n\n## Business Model Templates\n\n### SaaS Financial Model\n\n**Revenue Drivers:**\n\n- New MRR (customers × ARPU)\n- Expansion MRR (upsells)\n- Contraction MRR (downgrades)\n- Churned MRR (lost customers)\n\n**Key Ratios:**\n\n- Gross margin: 75-85%\n- S&M as % revenue: 40-60% (early stage)\n- CAC payback: \u003C 12 months\n- Net retention: 100-120%\n\n**Example Projection:**\n\n```\nYear 1: $500K ARR, 50 customers, $100K MRR by Dec\nYear 2: $2.5M ARR, 200 customers, $208K MRR by Dec\nYear 3: $8M ARR, 600 customers, $667K MRR by Dec\n```\n\n### Marketplace Financial Model\n\n**Revenue Drivers:**\n\n- GMV (Gross Merchandise Value)\n- Take rate (% of GMV)\n- Net revenue = GMV × Take rate\n\n**Key Ratios:**\n\n- Take rate: 10-30% depending on category\n- CAC for buyers vs. sellers\n- Contribution margin: 60-70%\n\n**Example Projection:**\n\n```\nYear 1: $5M GMV, 15% take rate = $750K revenue\nYear 2: $20M GMV, 15% take rate = $3M revenue\nYear 3: $60M GMV, 15% take rate = $9M revenue\n```\n\n### E-Commerce Financial Model\n\n**Revenue Drivers:**\n\n- Traffic (visitors)\n- Conversion rate\n- Average order value (AOV)\n- Purchase frequency\n\n**Key Ratios:**\n\n- Gross margin: 40-60%\n- Contribution margin: 20-35%\n- CAC payback: 3-6 months\n\n### Services \u002F Agency Financial Model\n\n**Revenue Drivers:**\n\n- Billable hours or projects\n- Hourly rate or project fee\n- Utilization rate\n- Team capacity\n\n**Key Ratios:**\n\n- Gross margin: 50-70%\n- Utilization: 70-85%\n- Revenue per employee\n\n## Fundraising Integration\n\n### Funding Scenario Modeling\n\n**Pre-Money Valuation:**\nBased on metrics and comparables.\n\n**Dilution:**\n\n```\nPost-Money = Pre-Money + Investment\nDilution % = Investment \u002F Post-Money\n```\n\n**Use of Funds:**\nAllocate funding to extend runway and achieve milestones.\n\n**Example:**\n\n```\nRaise: $5M at $20M pre-money\nPost-Money: $25M\nDilution: 20%\n\nUse of Funds:\n- Product Development: $2M (40%)\n- Sales & Marketing: $2M (40%)\n- G&A and Operations: $0.5M (10%)\n- Working Capital: $0.5M (10%)\n```\n\n### Milestone-Based Planning\n\n**Identify Key Milestones:**\n\n- Product launch\n- First $1M ARR\n- Break-even on CAC\n- Series A fundraise\n\n**Funding Amount:**\nEnsure runway to achieve next milestone + 6 months buffer.\n\n## Common Pitfalls\n\n**Pitfall 1: Overly Optimistic Revenue**\n\n- New startups rarely hit aggressive projections\n- Use conservative customer acquisition assumptions\n- Model realistic churn rates\n\n**Pitfall 2: Underestimating Costs**\n\n- Add 20% buffer to expense estimates\n- Include fully-loaded compensation\n- Account for software and tools\n\n**Pitfall 3: Ignoring Cash Flow Timing**\n\n- Revenue ≠ cash (payment terms)\n- Expenses paid before revenue collected\n- Model cash conversion carefully\n\n**Pitfall 4: Static Headcount**\n\n- Hiring takes time (3-6 months to fill roles)\n- Ramp time for productivity (3-6 months)\n- Account for attrition (10-15% annually)\n\n**Pitfall 5: Not Scenario Planning**\n\n- Single scenario is never accurate\n- Always model conservative case\n- Plan for what you'll do if base case fails\n\n## Model Validation\n\n**Sanity Checks:**\n\n- [ ] Revenue growth rate is achievable (3x in Year 2, 2x in Year 3)\n- [ ] Unit economics are realistic (LTV\u002FCAC > 3, payback \u003C 18 months)\n- [ ] Burn multiple is reasonable (\u003C 2.0 in Year 2-3)\n- [ ] Headcount scales with revenue (revenue per employee growing)\n- [ ] Gross margin is appropriate for business model\n- [ ] S&M spending aligns with CAC and growth targets\n\n**Benchmark Against Peers:**\nCompare key metrics to similar companies at similar stage.\n\n**Investor Feedback:**\nShare model with advisors or investors for feedback on assumptions.\n\n\n## Quick Start\n\nTo create a startup financial model:\n\n1. **Define business model** - Revenue drivers and pricing\n2. **Project revenue** - Cohort-based with retention\n3. **Model costs** - COGS, S&M, R&D, G&A by month\n4. **Plan headcount** - Hiring by role and department\n5. **Calculate cash flow** - Revenue - expenses = burn\u002Frunway\n6. **Compute metrics** - CAC, LTV, burn multiple, runway\n7. **Create scenarios** - Conservative, base, optimistic\n8. **Validate assumptions** - Sanity check and benchmark\n9. **Integrate fundraising** - Model funding rounds and milestones\n",{"name":5,"tags":44,"tools":46,"source":47,"license":14,"description":7,"source_path":48,"source_commit":49},[45,24,23],"finance",[],"https:\u002F\u002Fgithub.com\u002Fwshobson\u002Fagents","plugins\u002Fstartup-business-analyst\u002Fskills\u002Fstartup-financial-modeling","4236bb91f8395b0435f1d8b8baf9e8e4c69a8620","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstartup-financial-modeling",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add monoes\u002Fmonomind --skill startup-financial-modeling",{"tool":65,"command":66},"bunx","bunx skills add monoes\u002Fmonomind --skill startup-financial-modeling",{"tool":68,"command":69},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill startup-financial-modeling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstartup-financial-modeling\u002FSKILL.md",true,[73,78],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1068,{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fdetails.md","REFERENCE","参考文档",2821,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstartup-financial-modeling\u002Freferences\u002Fdetails.md",[85,114,149,175,200,227],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":113},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":131,"publishedAt":113},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[121,126],{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[132,133,134,97,135,136,36,137,102,138,139,140,141,142,143,144,145,146,147,148],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":89,"licenseFileUrl":153,"sourceHtmlUrl":154,"categories":155,"keywords":159,"publishedAt":113},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[156],{"categoryNo":157,"categoryName":158,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000031","产品经理",[142,160,161,162,163,100,164,36,165,166,167,141,168,169,170,26,171,172,173,174],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","feature","problem statement","use","document",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":89,"licenseFileUrl":179,"sourceHtmlUrl":180,"categories":181,"keywords":185,"publishedAt":113},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[182],{"categoryNo":183,"categoryName":184,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000033","数据分析师",[102,142,186,187,188,189,100,173,36,190,191,192,193,167,194,195,196,197,198,199],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":212,"publishedAt":113},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[206,209],{"categoryNo":207,"categoryName":208,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":210,"categoryName":211,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000023","Skill与智能体开发",[213,214,215,216,188,217,218,219,220,101,221,222,223,102,105,194,224,225,226,196],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":231,"categories":232,"keywords":234,"publishedAt":113},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[233],{"categoryNo":210,"categoryName":211,"taxonomyType":124,"taxonomyTypeDesc":125},[215,235,236,237,238,239,23,188,240,241,138,242,243,244,105,194,245,246,196,247],"workflow architect","architect","trees","user journeys","branch","map","workflows","architecture","state","leadership","recovery","operations","systems"]