[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAQCDABZQKPDCA96YC1N9J":3,"skill-same:01M7FAQCDABZQKPDCA96YC1N9J":53},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7FAQCDABZQKPDCA96YC1N9J","capacity-and-demand-planning",null,"Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. Use this to plan staffing for expected volume, diagnose a queue that keeps growing, size support or fulfillment capacity, or decide whether a bottleneck needs more capacity or better flow.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fcapacity-and-demand-planning\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: capacity-and-demand-planning\ndescription: Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. Use this to plan staffing for expected volume, diagnose a queue that keeps growing, size support or fulfillment capacity, or decide whether a bottleneck needs more capacity or better flow.\n---\n\n# Capacity and demand planning\n\nThis is operational throughput — how much work the organization can absorb. Allocating people\nacross projects is portfolio work, handled in `pmo:portfolio-governance`.\n\n## Forecast demand honestly\n\nSeparate the three components, because they need different treatment:\n\n- **Baseline** — the steady rate, best estimated from your own history rather than from a plan.\n- **Trend** — the direction, measured over enough periods to distinguish it from noise.\n- **Spikes** — launches, seasonality, campaigns, incidents. Known spikes are a planning input;\n  unknown ones are what headroom is for.\n\nForecast in the unit the work actually arrives in — tickets, orders, shipments, minutes of handling\n— not in revenue. Revenue divided by an average is a forecast of an average, and averages are where\ncapacity planning goes to die.\n\n## Capacity is not headcount\n\nUsable capacity is people multiplied by available hours multiplied by the fraction spent on the work\nin question. The last term is the one everyone omits and it is rarely above 70%: meetings, training,\nholiday, and the interruptions that come with the job are real.\n\nPlan against realistic effective capacity. Planning at 100% guarantees the plan fails on its first\nordinary week.\n\n## Queues tell you before the dashboard does\n\nUtilization above roughly 80% makes wait times rise sharply and non-linearly — a system at 95% is not\nslightly slower than one at 85%, it is qualitatively worse. This is why \"we have spare capacity on\npaper\" coexists with a queue that never clears.\n\nWatch the **trend in queue age**, not the queue length. A stable-length queue whose oldest item keeps\ngetting older is a queue that is quietly failing its slowest customers.\n\n## Add capacity or fix flow\n\nBefore adding capacity, establish which it is:\n\n- **Genuine capacity shortfall** — arrival rate exceeds service rate at reasonable utilization. Add\n  capacity.\n- **Flow problem** — rework, handoffs, waiting on another team, batching. Adding capacity here adds\n  cost and often makes throughput worse by increasing coordination. Send this to\n  `operations:process-design`.\n\nThe tell: if work spends most of its life waiting rather than being worked, it is a flow problem.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Never\n\n- Plan against nominal headcount rather than effective capacity.\n- Run a critical queue at sustained high utilization and treat the wait times as a mystery.\n- Add capacity to a process you have not measured.\n- Forecast in aggregate currency when work arrives in discrete units.\n","# Capacity and demand planning\n\nThis is operational throughput — how much work the organization can absorb. Allocating people\nacross projects is portfolio work, handled in `pmo:portfolio-governance`.\n\n## Forecast demand honestly\n\nSeparate the three components, because they need different treatment:\n\n- **Baseline** — the steady rate, best estimated from your own history rather than from a plan.\n- **Trend** — the direction, measured over enough periods to distinguish it from noise.\n- **Spikes** — launches, seasonality, campaigns, incidents. Known spikes are a planning input;\n  unknown ones are what headroom is for.\n\nForecast in the unit the work actually arrives in — tickets, orders, shipments, minutes of handling\n— not in revenue. Revenue divided by an average is a forecast of an average, and averages are where\ncapacity planning goes to die.\n\n## Capacity is not headcount\n\nUsable capacity is people multiplied by available hours multiplied by the fraction spent on the work\nin question. The last term is the one everyone omits and it is rarely above 70%: meetings, training,\nholiday, and the interruptions that come with the job are real.\n\nPlan against realistic effective capacity. Planning at 100% guarantees the plan fails on its first\nordinary week.\n\n## Queues tell you before the dashboard does\n\nUtilization above roughly 80% makes wait times rise sharply and non-linearly — a system at 95% is not\nslightly slower than one at 85%, it is qualitatively worse. This is why \"we have spare capacity on\npaper\" coexists with a queue that never clears.\n\nWatch the **trend in queue age**, not the queue length. A stable-length queue whose oldest item keeps\ngetting older is a queue that is quietly failing its slowest customers.\n\n## Add capacity or fix flow\n\nBefore adding capacity, establish which it is:\n\n- **Genuine capacity shortfall** — arrival rate exceeds service rate at reasonable utilization. Add\n  capacity.\n- **Flow problem** — rework, handoffs, waiting on another team, batching. Adding capacity here adds\n  cost and often makes throughput worse by increasing coordination. Send this to\n  `operations:process-design`.\n\nThe tell: if work spends most of its life waiting rather than being worked, it is a flow problem.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Never\n\n- Plan against nominal headcount rather than effective capacity.\n- Run a critical queue at sustained high utilization and treat the wait times as a mystery.\n- Add capacity to a process you have not measured.\n- Forecast in aggregate currency when work arrives in discrete units.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fcapacity-and-demand-planning",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add siddu1004\u002FSFP --skill capacity-and-demand-planning",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill capacity-and-demand-planning",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill capacity-and-demand-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fcapacity-and-demand-planning\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",929,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fcapacity-and-demand-planning\u002Freferences\u002Fsources.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\u002FSKILL.md",[],[],{"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},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\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},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\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},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\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},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]