[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MEZWGVH049Z6WH4ME1EAV":3,"skill-same:01M71MEZWGVH049Z6WH4ME1EAV":77},{"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":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M71MEZWGVH049Z6WH4ME1EAV","capacity-plan",null,"Plan resource capacity — workload analysis and utilization forecasting. Use when heading into quarterly planning, the team feels overallocated and you need the numbers, deciding whether to hire or deprioritize, or stress-testing whether upcoming projects fit the people you have.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcapacity-plan\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcapacity-plan\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"plan","capacity plan","capacity","https","operations","github","forecasting","hire","work","team","analysis","you","when","people","use","knowledge","testing","fit","planning","projects","2026-11-10 10:56:23",false,"---\nname: capacity-plan\ndescription: \"Plan resource capacity — workload analysis and utilization forecasting. Use when heading into quarterly planning, the team feels overallocated and you need the numbers, deciding whether to hire or deprioritize, or stress-testing whether upcoming projects fit the people you have.\"\ntags: []\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\nsource_path: \"operations\u002Fskills\u002Fcapacity-plan\"\nsource_commit: 8444efcd48f7012f09797778a36a33e73d0861f4\n---\n# \u002Fcapacity-plan\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nAnalyze team capacity and plan resource allocation.\n\n## Usage\n\n```\n\u002Fcapacity-plan $ARGUMENTS\n```\n\n## What I Need From You\n\n- **Team size and roles**: Who do you have?\n- **Current workload**: What are they working on? (Upload from project tracker or describe)\n- **Upcoming work**: What's coming next quarter?\n- **Constraints**: Budget, hiring timeline, skill requirements\n\n## Planning Dimensions\n\n### People\n- Available headcount and skills\n- Current allocation and utilization\n- Planned hires and timeline\n- Contractor and vendor capacity\n\n### Budget\n- Operating budget by category\n- Project-specific budgets\n- Variance tracking\n- Forecast vs. actual\n\n### Time\n- Project timelines and dependencies\n- Critical path analysis\n- Buffer and contingency planning\n- Deadline management\n\n## Utilization Targets\n\n| Role Type | Target Utilization | Notes |\n|-----------|-------------------|-------|\n| IC \u002F Specialist | 75-80% | Leave room for reactive work and growth |\n| Manager | 60-70% | Management overhead, meetings, 1:1s |\n| On-call \u002F Support | 50-60% | Interrupt-driven work is unpredictable |\n\n## Common Pitfalls\n\n- Planning to 100% utilization (no buffer for surprises)\n- Ignoring meeting load and context-switching costs\n- Not accounting for vacation, holidays, and sick time\n- Treating all hours as equal (creative work ≠ admin work)\n\n## Output\n\n```markdown\n## Capacity Plan: [Team\u002FProject]\n**Period:** [Date range] | **Team Size:** [X]\n\n### Current Utilization\n| Person\u002FRole | Capacity | Allocated | Available | Utilization |\n|-------------|----------|-----------|-----------|-------------|\n| [Name\u002FRole] | [hrs\u002Fwk] | [hrs\u002Fwk] | [hrs\u002Fwk] | [X]% |\n\n### Capacity Summary\n- **Total capacity**: [X] hours\u002Fweek\n- **Currently allocated**: [X] hours\u002Fweek ([X]%)\n- **Available**: [X] hours\u002Fweek ([X]%)\n- **Overallocated**: [X people above 100%]\n\n### Upcoming Demand\n| Project\u002FInitiative | Start | End | Resources Needed | Gap |\n|--------------------|-------|-----|-----------------|-----|\n| [Project] | [Date] | [Date] | [X FTEs] | [Covered\u002FGap] |\n\n### Bottlenecks\n- [Skill or role that's oversubscribed]\n- [Time period with a crunch]\n\n### Recommendations\n1. [Hire \u002F Contract \u002F Reprioritize \u002F Delay]\n2. [Specific action]\n\n### Scenarios\n| Scenario | Outcome |\n|----------|---------|\n| Do nothing | [What happens] |\n| Hire [X] | [What changes] |\n| Deprioritize [Y] | [What frees up] |\n```\n\n## If Connectors Available\n\nIf **~~project tracker** is connected:\n- Pull current workload and ticket assignments automatically\n- Show upcoming sprint or quarter commitments per person\n\nIf **~~calendar** is connected:\n- Factor in PTO, holidays, and recurring meeting load\n- Calculate actual available hours per person\n\n## Tips\n\n1. **Include all work** — BAU, projects, support, meetings. People aren't 100% available for project work.\n2. **Plan for buffer** — Target 80% utilization. 100% means no room for surprises.\n3. **Update regularly** — Capacity plans go stale fast. Review monthly.\n","# \u002Fcapacity-plan\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nAnalyze team capacity and plan resource allocation.\n\n## Usage\n\n```\n\u002Fcapacity-plan $ARGUMENTS\n```\n\n## What I Need From You\n\n- **Team size and roles**: Who do you have?\n- **Current workload**: What are they working on? (Upload from project tracker or describe)\n- **Upcoming work**: What's coming next quarter?\n- **Constraints**: Budget, hiring timeline, skill requirements\n\n## Planning Dimensions\n\n### People\n- Available headcount and skills\n- Current allocation and utilization\n- Planned hires and timeline\n- Contractor and vendor capacity\n\n### Budget\n- Operating budget by category\n- Project-specific budgets\n- Variance tracking\n- Forecast vs. actual\n\n### Time\n- Project timelines and dependencies\n- Critical path analysis\n- Buffer and contingency planning\n- Deadline management\n\n## Utilization Targets\n\n| Role Type | Target Utilization | Notes |\n|-----------|-------------------|-------|\n| IC \u002F Specialist | 75-80% | Leave room for reactive work and growth |\n| Manager | 60-70% | Management overhead, meetings, 1:1s |\n| On-call \u002F Support | 50-60% | Interrupt-driven work is unpredictable |\n\n## Common Pitfalls\n\n- Planning to 100% utilization (no buffer for surprises)\n- Ignoring meeting load and context-switching costs\n- Not accounting for vacation, holidays, and sick time\n- Treating all hours as equal (creative work ≠ admin work)\n\n## Output\n\n```markdown\n## Capacity Plan: [Team\u002FProject]\n**Period:** [Date range] | **Team Size:** [X]\n\n### Current Utilization\n| Person\u002FRole | Capacity | Allocated | Available | Utilization |\n|-------------|----------|-----------|-----------|-------------|\n| [Name\u002FRole] | [hrs\u002Fwk] | [hrs\u002Fwk] | [hrs\u002Fwk] | [X]% |\n\n### Capacity Summary\n- **Total capacity**: [X] hours\u002Fweek\n- **Currently allocated**: [X] hours\u002Fweek ([X]%)\n- **Available**: [X] hours\u002Fweek ([X]%)\n- **Overallocated**: [X people above 100%]\n\n### Upcoming Demand\n| Project\u002FInitiative | Start | End | Resources Needed | Gap |\n|--------------------|-------|-----|-----------------|-----|\n| [Project] | [Date] | [Date] | [X FTEs] | [Covered\u002FGap] |\n\n### Bottlenecks\n- [Skill or role that's oversubscribed]\n- [Time period with a crunch]\n\n### Recommendations\n1. [Hire \u002F Contract \u002F Reprioritize \u002F Delay]\n2. [Specific action]\n\n### Scenarios\n| Scenario | Outcome |\n|----------|---------|\n| Do nothing | [What happens] |\n| Hire [X] | [What changes] |\n| Deprioritize [Y] | [What frees up] |\n```\n\n## If Connectors Available\n\nIf **~~project tracker** is connected:\n- Pull current workload and ticket assignments automatically\n- Show upcoming sprint or quarter commitments per person\n\nIf **~~calendar** is connected:\n- Factor in PTO, holidays, and recurring meeting load\n- Calculate actual available hours per person\n\n## Tips\n\n1. **Include all work** — BAU, projects, support, meetings. People aren't 100% available for project work.\n2. **Plan for buffer** — Target 80% utilization. 100% means no room for surprises.\n3. **Update regularly** — Capacity plans go stale fast. Review monthly.\n",{"name":5,"tags":44,"tools":45,"source":46,"license":14,"description":7,"source_path":47,"source_commit":48},[],[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","operations\u002Fskills\u002Fcapacity-plan","8444efcd48f7012f09797778a36a33e73d0861f4","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcapacity-plan",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-14 03:30:52",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add monoes\u002Fmonomind --skill capacity-plan",{"tool":64,"command":65},"bunx","bunx skills add monoes\u002Fmonomind --skill capacity-plan",{"tool":67,"command":68},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill capacity-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcapacity-plan\u002FSKILL.md",true,[72],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11607,[78,105,139,164,187,214],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":104},"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.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[85,86,87,88,89,90,91,34,92,93,94,95,96,97,98,99,100,101,102,103],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":123,"publishedAt":104},"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.","MIT","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",[113,118],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[124,125,126,89,127,128,31,30,93,129,130,19,131,132,133,134,135,136,137,138],"writing","writing plans","plans","superpowers","implementation plan","code","tasks","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":149,"publishedAt":104},"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",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000031","产品经理",[132,150,151,152,153,34,154,31,155,156,27,131,157,158,159,160,161,162,33,163],"write spec","spec","user request","problem","acceptance","ask","vague","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":174,"publishedAt":104},"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",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000033","数据分析师",[93,132,175,176,177,178,34,33,31,179,180,181,182,27,24,183,22,184,185,186],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","sql","syntax","plugins","data",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":199,"publishedAt":104},"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",[193,196],{"categoryNo":194,"categoryName":195,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":197,"categoryName":198,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000023","Skill与智能体开发",[200,201,202,203,177,204,205,206,207,92,208,209,210,93,96,24,211,212,213,22],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":221,"publishedAt":104},"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",[220],{"categoryNo":197,"categoryName":198,"taxonomyType":116,"taxonomyTypeDesc":117},[202,222,223,224,225,226,37,177,227,228,129,229,230,231,96,24,232,23,22,233],"workflow architect","architect","trees","user journeys","branch","map","workflows","architecture","state","leadership","recovery","systems"]