[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASF0NVC5XB3ZR2RM3Y2289":3,"skill-same:01M7ASF0NVC5XB3ZR2RM3Y2289":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7ASF0NVC5XB3ZR2RM3Y2289","product-brainstorming",null,"Use before building a feature, product or component when the problem, users or scope are not yet settled — including requests phrased as \"build X\", \"add X\" or \"we need X\" that have not stated who it is for or what breaks without it. Produces a scoped brief, not an implementation.","badrabbitt\u002Fleanrigor","badrabbitt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F91770919?v=4","01M7ASDXHKQ5D169TY5S4VJPTK","01M7ASDXJADMY7PNQC14E2NEH2",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fskills\u002Fproduct-brainstorming\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: product-brainstorming\ndescription: Use before building a feature, product or component when the problem, users or scope are not yet settled — including requests phrased as \"build X\", \"add X\" or \"we need X\" that have not stated who it is for or what breaks without it. Produces a scoped brief, not an implementation.\nlicense: Apache-2.0\n---\n\n# Product brainstorming\n\nA request names a solution. This skill recovers the problem behind it, so the\nsolution can be judged rather than merely built.\n\n## When to stop and use this\n\nUse it when any of these is unknown: who has the problem, what they do today,\nwhat \"better\" means, or what is out of scope. Skip it when the user has already\nanswered those, or when the task is a defect fix with a known correct behaviour.\n\n## Produce this brief\n\nWrite it to `product-brief.md`. Six sections, each short. An empty section is a\nfinding, not a gap to fill with plausible text.\n\n### 1. Problem\nWhat goes wrong today, for whom, how often. Written so someone who disagrees\ncould point at the sentence they dispute.\n\n### 2. Users\nWho has this problem. Distinguish the person who feels the pain from the person\nwho chooses the tool — they are often different, and they want different things.\n\n### 3. Current behaviour\nWhat they do now, including the workaround they already have. A workaround that\nis good enough is the strongest argument against building anything.\n\n### 4. Alternatives\nAt least three: do nothing, the smallest change, and the requested solution.\nState what each costs and what it fails to solve. If the requested solution does\nnot win, say so.\n\n### 5. Scope\nIn scope, out of scope, and explicitly deferred. Out-of-scope items are named,\nnot omitted — an unnamed exclusion reappears as a surprise.\n\n### 6. Validation\nThe observation that would show this worked, and the observation that would show\nit did not. Both must be things you could actually see.\n\n## How to ask\n\nAsk the smallest number of questions that would change the design, one topic at\na time. Do not present a questionnaire. When you can answer a question from the\nrepository or the conversation, answer it yourself and say what you assumed.\n\n**Asking is not a substitute for the brief.** If nobody answers — because the\nsession is non-interactive, or the person is not there — write the brief anyway\nfrom what you have, and record each unknown as a stated assumption. A question\nleft hanging produces nothing; a brief with three explicit assumptions can be\ncorrected.\n\n## Disagreement is part of the job\n\nIf the brief shows the requested solution is wrong for the stated problem, say\nso in one or two sentences, then continue: produce the brief for the request as\ngiven, with the concern recorded. The decision belongs to the user.\n\n## Anti-patterns\n\n- Inventing users, numbers or pain that nobody stated.\n- Listing alternatives that were never real, to make one option look inevitable.\n- A validation section that cannot fail.\n- Sliding into implementation while the problem is still open.\n","# Product brainstorming\n\nA request names a solution. This skill recovers the problem behind it, so the\nsolution can be judged rather than merely built.\n\n## When to stop and use this\n\nUse it when any of these is unknown: who has the problem, what they do today,\nwhat \"better\" means, or what is out of scope. Skip it when the user has already\nanswered those, or when the task is a defect fix with a known correct behaviour.\n\n## Produce this brief\n\nWrite it to `product-brief.md`. Six sections, each short. An empty section is a\nfinding, not a gap to fill with plausible text.\n\n### 1. Problem\nWhat goes wrong today, for whom, how often. Written so someone who disagrees\ncould point at the sentence they dispute.\n\n### 2. Users\nWho has this problem. Distinguish the person who feels the pain from the person\nwho chooses the tool — they are often different, and they want different things.\n\n### 3. Current behaviour\nWhat they do now, including the workaround they already have. A workaround that\nis good enough is the strongest argument against building anything.\n\n### 4. Alternatives\nAt least three: do nothing, the smallest change, and the requested solution.\nState what each costs and what it fails to solve. If the requested solution does\nnot win, say so.\n\n### 5. Scope\nIn scope, out of scope, and explicitly deferred. Out-of-scope items are named,\nnot omitted — an unnamed exclusion reappears as a surprise.\n\n### 6. Validation\nThe observation that would show this worked, and the observation that would show\nit did not. Both must be things you could actually see.\n\n## How to ask\n\nAsk the smallest number of questions that would change the design, one topic at\na time. Do not present a questionnaire. When you can answer a question from the\nrepository or the conversation, answer it yourself and say what you assumed.\n\n**Asking is not a substitute for the brief.** If nobody answers — because the\nsession is non-interactive, or the person is not there — write the brief anyway\nfrom what you have, and record each unknown as a stated assumption. A question\nleft hanging produces nothing; a brief with three explicit assumptions can be\ncorrected.\n\n## Disagreement is part of the job\n\nIf the brief shows the requested solution is wrong for the stated problem, say\nso in one or two sentences, then continue: produce the brief for the request as\ngiven, with the concern recorded. The decision belongs to the user.\n\n## Anti-patterns\n\n- Inventing users, numbers or pain that nobody stated.\n- Listing alternatives that were never real, to make one option look inevitable.\n- A validation section that cannot fail.\n- Sliding into implementation while the problem is still open.\n",{"name":5,"license":14,"description":7},"main","0b45d399b5a5d7a6666c1df2b2218e4a0cddb8cc","skills\u002Fproduct-brainstorming",1,"https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor","https:\u002F\u002Fgithub.com\u002Fbadrabbitt","2026-10-13 17:15:33",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add badrabbitt\u002Fleanrigor --skill product-brainstorming",{"tool":36,"command":37},"bunx","bunx skills add badrabbitt\u002Fleanrigor --skill product-brainstorming",{"tool":39,"command":40},"pnpm","pnpm dlx skills add badrabbitt\u002Fleanrigor --skill product-brainstorming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fskills\u002Fproduct-brainstorming\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"leanrigor.yaml","REFERENCE","参考文档",261,"https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fskills\u002Fproduct-brainstorming\u002Fleanrigor.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"provenance.yaml",391,"https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fskills\u002Fproduct-brainstorming\u002Fprovenance.yaml",[55,62,69,75,83,89],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7ASF9ZY5ZT88M951GTRP6S9","verification","Use before claiming that work is complete, fixed, passing or done — including before committing, opening a pull request or reporting a result. Requires running the checks and quoting their real output instead of asserting success.","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M7ASF5TM4PNTA7B55384270G","senior-system-design","Use when designing or reviewing a system, service, migration or cross-component feature — anything where load, failure, data shape, security boundaries or rollout matter. Produces a design with explicit non-functional requirements, capacity assumptions, failure modes, security boundaries, observability and a rollout plan.","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fskills\u002Fsenior-system-design\u002FSKILL.md",[],[],{"skillNo":70,"name":57,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7ASEYCAQ7RRY7215KWQF2VB","Collect evidence before claiming that work is complete. Use when a task is about to be reported as done, fixed or passing.","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-router\u002Ftest\u002Ffixtures\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7ASEV2E8BHTP0Q0TA7AP2PQ","undeclared-network","A skill shipping a script that reaches the network without declaring the capability.","MIT","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-router\u002Ftest\u002Ffixtures\u002Fskills\u002Fundeclared-network\u002FSKILL.md",[],[],{"skillNo":84,"name":64,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7ASERMH0E0Q44E280RWDEGS","Produce a system design with explicit non-functional requirements, capacity assumptions, failure modes, security boundaries, observability and rollout.","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-router\u002Ftest\u002Ffixtures\u002Fskills\u002Fsenior-system-design\u002FSKILL.md",[],[],{"skillNo":90,"name":5,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M7ASEN6GGQ3NGWBKWDH805RR","Explore the problem, users, alternatives, scope and validation before any implementation work begins.","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-router\u002Ftest\u002Ffixtures\u002Fskills\u002Fproduct-brainstorming\u002FSKILL.md",[],[]]