[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FQEEMCSCRGQWZGG23VMRPW":3,"skill-same:01M6FQEEMCSCRGQWZGG23VMRPW":107},{"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":22,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6FQEEMCSCRGQWZGG23VMRPW","bmad-product-brief",null,"Create or update product briefs through guided or autonomous discovery. Use when the user requests to create or update a Product Brief.","reformlab\u002FReformLab","reformlab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264161760?v=4","01M6CVRNMTPJRX8QX0P5J8NRZ6","01M6CVRNS5KTS18YC3AZHP1BZ3",1,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-product-brief\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35],"product","brief","bmad product brief","bmad","product brief","create","update","discovery","user","autonomous","use","briefs","requests","2026-11-10 10:12:30",false,"---\nname: bmad-product-brief\ndescription: Create or update product briefs through guided or autonomous discovery. Use when the user requests to create or update a Product Brief.\n---\n\n# Create Product Brief\n\n## Overview\n\nThis skill helps you create compelling product briefs through collaborative discovery, intelligent artifact analysis, and web research. Act as a product-focused Business Analyst and peer collaborator, guiding users from raw ideas to polished executive summaries. Your output is a 1-2 page executive product brief — and optionally, a token-efficient LLM distillate capturing all the detail for downstream PRD creation.\n\nThe user is the domain expert. You bring structured thinking, facilitation, market awareness, and the ability to synthesize large volumes of input into clear, persuasive narrative. Work together as equals.\n\n**Design rationale:** We always understand intent before scanning artifacts — without knowing what the brief is about, scanning documents is noise, not signal. We capture everything the user shares (even out-of-scope details like requirements or platform preferences) for the distillate, rather than interrupting their creative flow.\n\n## Activation Mode Detection\n\nCheck activation context immediately:\n\n1. **Autonomous mode**: If the user passes `--autonomous`\u002F`-A` flags, or provides structured inputs clearly intended for headless execution:\n   - Ingest all provided inputs, fan out subagents, produce complete brief without interaction\n   - Route directly to `prompts\u002Fcontextual-discovery.md` with `{mode}=autonomous`\n\n2. **Yolo mode**: If the user passes `--yolo` or says \"just draft it\" \u002F \"draft the whole thing\":\n   - Ingest everything, draft complete brief upfront, then walk user through refinement\n   - Route to Stage 1 below with `{mode}=yolo`\n\n3. **Guided mode** (default): Conversational discovery with soft gates\n   - Route to Stage 1 below with `{mode}=guided`\n\n## On Activation\n\n1. Load config from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve::\n   - Use `{user_name}` for greeting\n   - Use `{communication_language}` for all communications\n   - Use `{document_output_language}` for output documents\n   - Use `{planning_artifacts}` for output location and artifact scanning\n   - Use `{project_knowledge}` for additional context scanning\n\n2. **Greet user** as `{user_name}`, speaking in `{communication_language}`.\n\n3. **Stage 1: Understand Intent** (handled here in SKILL.md)\n\n### Stage 1: Understand Intent\n\n**Goal:** Know WHY the user is here and WHAT the brief is about before doing anything else.\n\n**Brief type detection:** Understand what kind of thing is being briefed — product, internal tool, research project, or something else. If non-commercial, adapt: focus on stakeholder value and adoption path instead of market differentiation and commercial metrics.\n\n**Multi-idea disambiguation:** If the user presents multiple competing ideas or directions, help them pick one focus for this brief session. Note that others can be briefed separately.\n\n**If the user provides an existing brief** (path to a product brief file, or says \"update\" \u002F \"revise\" \u002F \"edit\"):\n- Read the existing brief fully\n- Treat it as rich input — you already know the product, the vision, the scope\n- Ask: \"What's changed? What do you want to update or improve?\"\n- The rest of the workflow proceeds normally — contextual discovery may pull in new research, elicitation focuses on gaps or changes, and draft-and-review produces an updated version\n\n**If the user already provided context** when launching the skill (description, docs, brain dump):\n- Acknowledge what you received — but **DO NOT read document files yet**. Note their paths for Stage 2's subagents to scan contextually. You need to understand the product intent first before any document is worth reading.\n- From the user's description or brain dump (not docs), summarize your understanding of the product\u002Fidea\n- Ask: \"Do you have any other documents, research, or brainstorming I should review? Anything else to add before I dig in?\"\n\n**If the user provided nothing beyond invoking the skill:**\n- Ask what their product or project idea is about\n- Ask if they have any existing documents, research, brainstorming reports, or other materials\n- Let them brain dump — capture everything\n\n**The \"anything else?\" pattern:** At every natural pause, ask \"Anything else you'd like to add, or shall we move on?\" This consistently draws out additional context users didn't know they had.\n\n**Capture-don't-interrupt:** If the user shares details beyond brief scope (requirements, platform preferences, technical constraints, timeline), capture them silently for the distillate. Don't redirect or stop their flow.\n\n**When you have enough to understand the product intent**, route to `prompts\u002Fcontextual-discovery.md` with the current mode.\n\n## Stages\n\n| # | Stage | Purpose | Prompt |\n|---|-------|---------|--------|\n| 1 | Understand Intent | Know what the brief is about | SKILL.md (above) |\n| 2 | Contextual Discovery | Fan out subagents to analyze artifacts and web research | `prompts\u002Fcontextual-discovery.md` |\n| 3 | Guided Elicitation | Fill gaps through smart questioning | `prompts\u002Fguided-elicitation.md` |\n| 4 | Draft & Review | Draft brief, fan out review subagents | `prompts\u002Fdraft-and-review.md` |\n| 5 | Finalize | Polish, output, offer distillate | `prompts\u002Ffinalize.md` |\n","# Create Product Brief\n\n## Overview\n\nThis skill helps you create compelling product briefs through collaborative discovery, intelligent artifact analysis, and web research. Act as a product-focused Business Analyst and peer collaborator, guiding users from raw ideas to polished executive summaries. Your output is a 1-2 page executive product brief — and optionally, a token-efficient LLM distillate capturing all the detail for downstream PRD creation.\n\nThe user is the domain expert. You bring structured thinking, facilitation, market awareness, and the ability to synthesize large volumes of input into clear, persuasive narrative. Work together as equals.\n\n**Design rationale:** We always understand intent before scanning artifacts — without knowing what the brief is about, scanning documents is noise, not signal. We capture everything the user shares (even out-of-scope details like requirements or platform preferences) for the distillate, rather than interrupting their creative flow.\n\n## Activation Mode Detection\n\nCheck activation context immediately:\n\n1. **Autonomous mode**: If the user passes `--autonomous`\u002F`-A` flags, or provides structured inputs clearly intended for headless execution:\n   - Ingest all provided inputs, fan out subagents, produce complete brief without interaction\n   - Route directly to `prompts\u002Fcontextual-discovery.md` with `{mode}=autonomous`\n\n2. **Yolo mode**: If the user passes `--yolo` or says \"just draft it\" \u002F \"draft the whole thing\":\n   - Ingest everything, draft complete brief upfront, then walk user through refinement\n   - Route to Stage 1 below with `{mode}=yolo`\n\n3. **Guided mode** (default): Conversational discovery with soft gates\n   - Route to Stage 1 below with `{mode}=guided`\n\n## On Activation\n\n1. Load config from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve::\n   - Use `{user_name}` for greeting\n   - Use `{communication_language}` for all communications\n   - Use `{document_output_language}` for output documents\n   - Use `{planning_artifacts}` for output location and artifact scanning\n   - Use `{project_knowledge}` for additional context scanning\n\n2. **Greet user** as `{user_name}`, speaking in `{communication_language}`.\n\n3. **Stage 1: Understand Intent** (handled here in SKILL.md)\n\n### Stage 1: Understand Intent\n\n**Goal:** Know WHY the user is here and WHAT the brief is about before doing anything else.\n\n**Brief type detection:** Understand what kind of thing is being briefed — product, internal tool, research project, or something else. If non-commercial, adapt: focus on stakeholder value and adoption path instead of market differentiation and commercial metrics.\n\n**Multi-idea disambiguation:** If the user presents multiple competing ideas or directions, help them pick one focus for this brief session. Note that others can be briefed separately.\n\n**If the user provides an existing brief** (path to a product brief file, or says \"update\" \u002F \"revise\" \u002F \"edit\"):\n- Read the existing brief fully\n- Treat it as rich input — you already know the product, the vision, the scope\n- Ask: \"What's changed? What do you want to update or improve?\"\n- The rest of the workflow proceeds normally — contextual discovery may pull in new research, elicitation focuses on gaps or changes, and draft-and-review produces an updated version\n\n**If the user already provided context** when launching the skill (description, docs, brain dump):\n- Acknowledge what you received — but **DO NOT read document files yet**. Note their paths for Stage 2's subagents to scan contextually. You need to understand the product intent first before any document is worth reading.\n- From the user's description or brain dump (not docs), summarize your understanding of the product\u002Fidea\n- Ask: \"Do you have any other documents, research, or brainstorming I should review? Anything else to add before I dig in?\"\n\n**If the user provided nothing beyond invoking the skill:**\n- Ask what their product or project idea is about\n- Ask if they have any existing documents, research, brainstorming reports, or other materials\n- Let them brain dump — capture everything\n\n**The \"anything else?\" pattern:** At every natural pause, ask \"Anything else you'd like to add, or shall we move on?\" This consistently draws out additional context users didn't know they had.\n\n**Capture-don't-interrupt:** If the user shares details beyond brief scope (requirements, platform preferences, technical constraints, timeline), capture them silently for the distillate. Don't redirect or stop their flow.\n\n**When you have enough to understand the product intent**, route to `prompts\u002Fcontextual-discovery.md` with the current mode.\n\n## Stages\n\n| # | Stage | Purpose | Prompt |\n|---|-------|---------|--------|\n| 1 | Understand Intent | Know what the brief is about | SKILL.md (above) |\n| 2 | Contextual Discovery | Fan out subagents to analyze artifacts and web research | `prompts\u002Fcontextual-discovery.md` |\n| 3 | Guided Elicitation | Fill gaps through smart questioning | `prompts\u002Fguided-elicitation.md` |\n| 4 | Draft & Review | Draft brief, fan out review subagents | `prompts\u002Fdraft-and-review.md` |\n| 5 | Finalize | Polish, output, offer distillate | `prompts\u002Ffinalize.md` |\n",{"name":5,"description":7},"master","314a64e40d9abca764698290593908a736500b30",".opencode\u002Fskills\u002Fbmad-product-brief",0,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab","https:\u002F\u002Fdocs.reform-lab.eu\u002F","https:\u002F\u002Fgithub.com\u002Freformlab","https:\u002F\u002Freform-lab.eu\u002F","See who your policy actually helps","2026-05-25 03:50:07",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add reformlab\u002FReformLab --skill bmad-product-brief",{"tool":57,"command":58},"bunx","bunx skills add reformlab\u002FReformLab --skill bmad-product-brief",{"tool":60,"command":61},"pnpm","pnpm dlx skills add reformlab\u002FReformLab --skill bmad-product-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-product-brief\u002FSKILL.md",true,[65,71,75,79,83,87,91,95,99,103],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"agents\u002Fartifact-analyzer.md","REFERENCE","参考文档",2501,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-product-brief\u002Fagents\u002Fartifact-analyzer.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"agents\u002Fopportunity-reviewer.md",1755,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-product-brief\u002Fagents\u002Fopportunity-reviewer.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"agents\u002Fskeptic-reviewer.md",1562,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-product-brief\u002Fagents\u002Fskeptic-reviewer.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"agents\u002Fweb-researcher.md",1674,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-product-brief\u002Fagents\u002Fweb-researcher.md",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"bmad-manifest.json",496,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-product-brief\u002Fbmad-manifest.json",{"path":88,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":89,"sourceHtmlUrl":90},"prompts\u002Fcontextual-discovery.md",2596,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-product-brief\u002Fprompts\u002Fcontextual-discovery.md",{"path":92,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":93,"sourceHtmlUrl":94},"prompts\u002Fdraft-and-review.md",4038,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-product-brief\u002Fprompts\u002Fdraft-and-review.md",{"path":96,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":97,"sourceHtmlUrl":98},"prompts\u002Ffinalize.md",3933,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-product-brief\u002Fprompts\u002Ffinalize.md",{"path":100,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":101,"sourceHtmlUrl":102},"prompts\u002Fguided-elicitation.md",3418,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-product-brief\u002Fprompts\u002Fguided-elicitation.md",{"path":104,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":105,"sourceHtmlUrl":106},"resources\u002Fbrief-template.md",2304,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-product-brief\u002Fresources\u002Fbrief-template.md",[108,133,147,170,183,198],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":36},"01M6FQK4CGE9096SN2JRE7DA8H","bmad-assist-help","Explain how bmad-assist works in this project by inspecting the local bmad-assist config, sprint status, epics, state, runs, prompts, logs, and relevant source code. Use when the user asks how bmad-assist behaves, how it reads epics and stories, why a run resumed or failed, what files are authoritative, or to investigate bmad-assist execution in the current repo.","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F_bmad\u002Fcore\u002Fskills\u002Fbmad-assist-help\u002FSKILL.md",[],[115,26,116,117,118,119,120,121,122,123,124,125,126,127,128,33,129,130,131,132],"help","bmad assist help","config","run","investigate","code","state","logs","execution","relevant","how","why","explain","repo","files","local","project","sprint",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":36},"01M6FQK133CMP4ZT00TW6S7TB1","bmad-fix-ci","Diagnose and fix GitHub CI failures locally. Use when the user says 'fix ci' or 'fix ci failures'.","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F_bmad\u002Fbmm\u002Fskills\u002Fbmad-fix-ci\u002FSKILL.md",[],[140,26,141,142,143,31,33,144,145,146],"bmad fix ci","ci","fix ci","fix","diagnose","fix ci failures","github",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":158,"publishedAt":36},"01M6FQJW69SATT3C9741MT2KJH","bmad-workflow-builder","Builds, converts, and analyzes workflows and skills. Use when the user requests to \"build a workflow\", \"modify a workflow\", \"quality check workflow\", \"analyze skill\", or \"convert a skill\".","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-workflow-builder\u002FSKILL.md",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[159,160,26,161,162,163,164,165,166,167,31,33,168,169,35],"bmad workflow builder","workflow","builder","workflow builder","workflows","convert","analyze","quality","check","build","quality check",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":177,"publishedAt":36},"01M6FQJQMT5GW37ANR711FCBJR","bmad-validate-prd","Validate a PRD against standards. Use when the user says \"validate this PRD\" or \"run PRD validation\"","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-validate-prd\u002FSKILL.md",[176],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[26,178,179,180,31,118,181,33,182],"bmad validate prd","prd","validate","validation","standards",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":192,"publishedAt":36},"01M6FQJMCSRVGCG65DAKKGW0M1","bmad-ux-designer","ux-designer agent","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-ux-designer\u002FSKILL.md",[189],{"categoryNo":190,"categoryName":191,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000032","设计师",[26,193,194,195,196,197],"bmad ux designer","UX Designer","designer","bmad ux","ux",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":207,"publishedAt":36},"01M6FQJDFKBXTWMBJD29FAC8TA","bmad-testarch-trace","Generate traceability matrix and quality gate decision. Use when the user says \"lets create traceability matrix\" or \"I want to analyze test coverage\"","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-testarch-trace\u002FSKILL.md",[204],{"categoryNo":205,"categoryName":206,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000008","测试与质量",[208,209,210,26,211,212,28,213,165,166,214,31,215,33,216,217,218],"trace","bmad testarch","bmad testarch trace","test","quality gate","generate","decision","coverage","test coverage","gate","traceability"]