[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBBJFS8M83QEENC990Z278":3,"skill-same:01M7FBBJFS8M83QEENC990Z278":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},"01M7FBBJFS8M83QEENC990Z278","process-design",null,"Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process.","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\u002Fprocess-design\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: process-design\ndescription: Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process.\n---\n\n# Process design\n\n## Map what happens, not what is supposed to happen\n\nFollow a real instance end to end and record every step, handoff, wait, and rework loop. Talk to the\npeople doing it, who will describe several steps that exist nowhere in the documentation and one or\ntwo that everyone has quietly stopped doing.\n\nThen measure two things:\n\n- **Touch time** — how long the work actually takes.\n- **Elapsed time** — how long it takes to get through.\n\nThe gap between them is the process. In most broken processes, work is waiting more than ninety\npercent of the time, which means speeding up the work changes almost nothing. Attack the waits.\n\n## Find the real constraint\n\nOne step governs throughput. Improving anything else produces inventory in front of the constraint\nand no more output. Find it: the step with a queue in front of it.\n\nCommon constraints that are not the obvious step: a single approver, a specialist everything routes\nthrough, a system that only one team can access, and a batch cycle that makes everything wait for\nthe weekly run.\n\n## Redesign\n\nIn this order, because the order is the leverage:\n\n1. **Eliminate.** Does this step need to exist? Many exist to catch a failure that a different fix\n   would prevent entirely.\n2. **Simplify.** Fewer handoffs, fewer approvals, fewer systems. Every handoff is a place work\n   stops.\n3. **Standardize.** One way of doing it, written down, with the decision rules explicit.\n4. **Automate.** Last. Automating an unexamined process makes a bad process faster and much harder\n   to change.\n\nPush approval to the lowest level that can be accountable, and set thresholds so routine cases do\nnot queue behind exceptional ones.\n\n## Make it hold\n\nA documented process that relies on discipline degrades within a quarter. Build the control into the\nsystem: required fields, blocking gates, defaults that are correct, automated handoffs.\n\n**Never fix a recurring failure with a reminder.** If people are forgetting a step, the system\npermits forgetting it. Fix that.\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- Redesign from the documented process. Map what people actually do first.\n- Optimize a step that is not the constraint. Everything you speed up ahead of it just queues.\n- Add an approval to prevent a failure that happened once.\n- Hand over a process with no owner and no measure. It reverts within a quarter.\n\n## Return contract\n\nCurrent state with elapsed and touch time, the constraint and its evidence, the redesign, what it\ncosts to implement, and the measure that will show it worked.\n","# Process design\n\n## Map what happens, not what is supposed to happen\n\nFollow a real instance end to end and record every step, handoff, wait, and rework loop. Talk to the\npeople doing it, who will describe several steps that exist nowhere in the documentation and one or\ntwo that everyone has quietly stopped doing.\n\nThen measure two things:\n\n- **Touch time** — how long the work actually takes.\n- **Elapsed time** — how long it takes to get through.\n\nThe gap between them is the process. In most broken processes, work is waiting more than ninety\npercent of the time, which means speeding up the work changes almost nothing. Attack the waits.\n\n## Find the real constraint\n\nOne step governs throughput. Improving anything else produces inventory in front of the constraint\nand no more output. Find it: the step with a queue in front of it.\n\nCommon constraints that are not the obvious step: a single approver, a specialist everything routes\nthrough, a system that only one team can access, and a batch cycle that makes everything wait for\nthe weekly run.\n\n## Redesign\n\nIn this order, because the order is the leverage:\n\n1. **Eliminate.** Does this step need to exist? Many exist to catch a failure that a different fix\n   would prevent entirely.\n2. **Simplify.** Fewer handoffs, fewer approvals, fewer systems. Every handoff is a place work\n   stops.\n3. **Standardize.** One way of doing it, written down, with the decision rules explicit.\n4. **Automate.** Last. Automating an unexamined process makes a bad process faster and much harder\n   to change.\n\nPush approval to the lowest level that can be accountable, and set thresholds so routine cases do\nnot queue behind exceptional ones.\n\n## Make it hold\n\nA documented process that relies on discipline degrades within a quarter. Build the control into the\nsystem: required fields, blocking gates, defaults that are correct, automated handoffs.\n\n**Never fix a recurring failure with a reminder.** If people are forgetting a step, the system\npermits forgetting it. Fix that.\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- Redesign from the documented process. Map what people actually do first.\n- Optimize a step that is not the constraint. Everything you speed up ahead of it just queues.\n- Add an approval to prevent a failure that happened once.\n- Hand over a process with no owner and no measure. It reverts within a quarter.\n\n## Return contract\n\nCurrent state with elapsed and touch time, the constraint and its evidence, the redesign, what it\ncosts to implement, and the measure that will show it worked.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fprocess-design",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 process-design",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill process-design",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill process-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fprocess-design\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",1392,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fprocess-design\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",[],[]]