[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBCECP3Q97TKSBDY6RPTES":3,"skill-same:01M7FBCECP3Q97TKSBDY6RPTES":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},"01M7FBCECP3Q97TKSBDY6RPTES","product-requirements",null,"Writes down what is being built so a team can build it and know when they are done — problem and success measure before solution, scope stated by exclusion, user-visible behavior including the states everyone forgets, acceptance criteria someone can test, and the open questions named rather than buried. Use this to write a specification, review one that is causing rework, or work out why a delivered feature technically matched the request and still was not what anyone wanted.","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\u002Fproduct-requirements\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: product-requirements\ndescription: Writes down what is being built so a team can build it and know when they are done — problem and success measure before solution, scope stated by exclusion, user-visible behavior including the states everyone forgets, acceptance criteria someone can test, and the open questions named rather than buried. Use this to write a specification, review one that is causing rework, or work out why a delivered feature technically matched the request and still was not what anyone wanted.\n---\n\n# Product requirements\n\nA specification exists to prevent expensive rediscovery — of decisions already made, of scope\nalready agreed, and of the edge cases that are found either now on a page or later in production.\n\n## Lead with the problem and the number, not the solution\n\nOpen with who has the problem, what it costs them today, and what you expect to change if this\nships — expressed as a measure with a target and a date. A document that starts with a solution\ninvites the team to optimize the wrong thing and gives you no way to tell afterward whether it\nworked.\n\n**Decide the success measure before building, not at launch.** A number chosen afterward is chosen\nto be met.\n\n## State scope by exclusion\n\nEveryone reads what is in scope and assumes the rest is coming. An explicit \"not in this\" list is\nthe cheapest thing in the document and prevents most scope arguments — including the ones that\narrive as clarifications rather than as requests.\n\nSay what is deferred versus what is rejected. Those are different, and conflating them means the\nrejected thing comes back.\n\n## Describe behavior, not implementation\n\nWrite what the user experiences and what the system guarantees. Leave the how to the people who\nwill own it — a specification that dictates implementation gets a worse implementation and blurs\nwho is accountable for it.\n\n**The states nobody writes down are where the rework comes from.** Empty, loading, error,\npartial, permission-denied, offline, and the first-run case with no data. Also: what happens to\nrecords that already exist, what happens at the limits, and what happens when two people do it at\nonce. Most \"that wasn't what I meant\" traces back to one of these.\n\n## Make acceptance criteria testable\n\nEach one should be a statement someone can evaluate as true or false without asking you. \"Fast\" and\n\"intuitive\" are not criteria; a response-time budget and a task someone completes unaided are.\n\nIf a criterion cannot be tested, it is either a principle — say so and move it — or it is not\nfinished being thought about.\n\n## Name the open questions and who owns them\n\nEvery specification has unknowns. Listing them, with an owner and a date needed by, is what\nseparates a document that is honestly incomplete from one that is quietly wrong. Buried\nuncertainty gets resolved by whoever hits it first, usually at the least convenient moment and\nwithout anyone noticing a decision was made.\n\n## Keep it alive, or state that it is frozen\n\nA specification that diverges from what was built becomes a trap for the next person. Either update\nit as decisions change, or mark it as-of-a-date and point at wherever the truth now lives. The\nworst outcome is a document that looks current and is not.\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- Open with a solution and leave the problem implied.\n- Ship a specification with no explicit out-of-scope list.\n- Write an acceptance criterion that requires asking you whether it passed.\n- Leave an unresolved question inside the body where it reads as a decision.\n","# Product requirements\n\nA specification exists to prevent expensive rediscovery — of decisions already made, of scope\nalready agreed, and of the edge cases that are found either now on a page or later in production.\n\n## Lead with the problem and the number, not the solution\n\nOpen with who has the problem, what it costs them today, and what you expect to change if this\nships — expressed as a measure with a target and a date. A document that starts with a solution\ninvites the team to optimize the wrong thing and gives you no way to tell afterward whether it\nworked.\n\n**Decide the success measure before building, not at launch.** A number chosen afterward is chosen\nto be met.\n\n## State scope by exclusion\n\nEveryone reads what is in scope and assumes the rest is coming. An explicit \"not in this\" list is\nthe cheapest thing in the document and prevents most scope arguments — including the ones that\narrive as clarifications rather than as requests.\n\nSay what is deferred versus what is rejected. Those are different, and conflating them means the\nrejected thing comes back.\n\n## Describe behavior, not implementation\n\nWrite what the user experiences and what the system guarantees. Leave the how to the people who\nwill own it — a specification that dictates implementation gets a worse implementation and blurs\nwho is accountable for it.\n\n**The states nobody writes down are where the rework comes from.** Empty, loading, error,\npartial, permission-denied, offline, and the first-run case with no data. Also: what happens to\nrecords that already exist, what happens at the limits, and what happens when two people do it at\nonce. Most \"that wasn't what I meant\" traces back to one of these.\n\n## Make acceptance criteria testable\n\nEach one should be a statement someone can evaluate as true or false without asking you. \"Fast\" and\n\"intuitive\" are not criteria; a response-time budget and a task someone completes unaided are.\n\nIf a criterion cannot be tested, it is either a principle — say so and move it — or it is not\nfinished being thought about.\n\n## Name the open questions and who owns them\n\nEvery specification has unknowns. Listing them, with an owner and a date needed by, is what\nseparates a document that is honestly incomplete from one that is quietly wrong. Buried\nuncertainty gets resolved by whoever hits it first, usually at the least convenient moment and\nwithout anyone noticing a decision was made.\n\n## Keep it alive, or state that it is frozen\n\nA specification that diverges from what was built becomes a trap for the next person. Either update\nit as decisions change, or mark it as-of-a-date and point at wherever the truth now lives. The\nworst outcome is a document that looks current and is not.\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- Open with a solution and leave the problem implied.\n- Ship a specification with no explicit out-of-scope list.\n- Write an acceptance criterion that requires asking you whether it passed.\n- Leave an unresolved question inside the body where it reads as a decision.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fproduct-requirements",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 product-requirements",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill product-requirements",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill product-requirements","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fproduct-requirements\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",4017,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fproduct-requirements\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",[],[]]