[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7533VRVFSBBAAWDMZG55Z6B":3,"skill-same:01M7533VRVFSBBAAWDMZG55Z6B":81},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7533VRVFSBBAAWDMZG55Z6B","bmad-domain-research",null,"Conduct domain and industry research. Use when the user says wants to do domain research for a topic or industry","flanliulf\u002FSpecLite","flanliulf","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3830171?v=4","01M752MYG3GGEADW105E2F6154","Fancy Liu","01M752MYGXQ0R06TYQG3BVVABS",4,"MIT","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fbmad-domain-research\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: bmad-domain-research\ndescription: 'Conduct domain and industry research. Use when the user says wants to do domain research for a topic or industry'\n---\n\n# Domain Research Workflow\n\n**Goal:** Conduct comprehensive domain\u002Findustry research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.\n\n**Your Role:** You are a domain research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.\n\n## Conventions\n\n- Bare paths (e.g. `domain-steps\u002Fstep-01-init.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## PREREQUISITE\n\n**⛔ Web search required.** If unavailable, abort and tell the user.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad 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\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## QUICK TOPIC DISCOVERY\n\n\"Welcome {{user_name}}! Let's get started with your **domain\u002Findustry research**.\n\n**What domain, industry, or sector do you want to research?**\n\nFor example:\n- 'The healthcare technology industry'\n- 'Sustainable packaging regulations in Europe'\n- 'Construction and building materials sector'\n- 'Or any other domain you have in mind...'\"\n\n### Topic Clarification\n\nBased on the user's topic, briefly clarify:\n1. **Core Domain**: \"What specific aspect of [domain] are you most interested in?\"\n2. **Research Goals**: \"What do you hope to achieve with this research?\"\n3. **Scope**: \"Should we focus broadly or dive deep into specific aspects?\"\n\n## ROUTE TO DOMAIN RESEARCH STEPS\n\nAfter gathering the topic and goals:\n\n1. Set `research_type = \"domain\"`\n2. Set `research_topic = [discovered topic from discussion]`\n3. Set `research_goals = [discovered goals from discussion]`\n4. Derive `research_topic_slug` from `{{research_topic}}`: lowercase, trim, replace whitespace with `-`, strip path separators (`\u002F`, `\\`), `..`, and any character that is not alphanumeric, `-`, or `_`. Collapse repeated `-` and strip leading\u002Ftrailing `-`. If the result is empty, use `untitled`.\n5. Create the starter output file: `{planning_artifacts}\u002Fresearch\u002Fdomain-{{research_topic_slug}}-research-{{date}}.md` with exact copy of the `.\u002Fresearch.template.md` contents\n6. Load: `.\u002Fdomain-steps\u002Fstep-01-init.md` with topic context\n\n**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask \"What do you want to research?\" again - it can focus on refining the scope for domain research.\n\n**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**\n","# Domain Research Workflow\n\n**Goal:** Conduct comprehensive domain\u002Findustry research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.\n\n**Your Role:** You are a domain research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.\n\n## Conventions\n\n- Bare paths (e.g. `domain-steps\u002Fstep-01-init.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## PREREQUISITE\n\n**⛔ Web search required.** If unavailable, abort and tell the user.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad 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\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## QUICK TOPIC DISCOVERY\n\n\"Welcome {{user_name}}! Let's get started with your **domain\u002Findustry research**.\n\n**What domain, industry, or sector do you want to research?**\n\nFor example:\n- 'The healthcare technology industry'\n- 'Sustainable packaging regulations in Europe'\n- 'Construction and building materials sector'\n- 'Or any other domain you have in mind...'\"\n\n### Topic Clarification\n\nBased on the user's topic, briefly clarify:\n1. **Core Domain**: \"What specific aspect of [domain] are you most interested in?\"\n2. **Research Goals**: \"What do you hope to achieve with this research?\"\n3. **Scope**: \"Should we focus broadly or dive deep into specific aspects?\"\n\n## ROUTE TO DOMAIN RESEARCH STEPS\n\nAfter gathering the topic and goals:\n\n1. Set `research_type = \"domain\"`\n2. Set `research_topic = [discovered topic from discussion]`\n3. Set `research_goals = [discovered goals from discussion]`\n4. Derive `research_topic_slug` from `{{research_topic}}`: lowercase, trim, replace whitespace with `-`, strip path separators (`\u002F`, `\\`), `..`, and any character that is not alphanumeric, `-`, or `_`. Collapse repeated `-` and strip leading\u002Ftrailing `-`. If the result is empty, use `untitled`.\n5. Create the starter output file: `{planning_artifacts}\u002Fresearch\u002Fdomain-{{research_topic_slug}}-research-{{date}}.md` with exact copy of the `.\u002Fresearch.template.md` contents\n6. Load: `.\u002Fdomain-steps\u002Fstep-01-init.md` with topic context\n\n**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask \"What do you want to research?\" again - it can focus on refining the scope for domain research.\n\n**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**\n",{"name":5,"description":7},"main","73fff74748dc0e27169d3ae76818d545bdbe8591",".kiro\u002Fskills\u002Fbmad-domain-research",0,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite","https:\u002F\u002Fgithub.com\u002Fflanliulf","2026-11-12 11:47:29",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add flanliulf\u002FSpecLite --skill bmad-domain-research",{"tool":37,"command":38},"bunx","bunx skills add flanliulf\u002FSpecLite --skill bmad-domain-research",{"tool":40,"command":41},"pnpm","pnpm dlx skills add flanliulf\u002FSpecLite --skill bmad-domain-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fbmad-domain-research\u002FSKILL.md",true,[45,51,57,61,65,69,73,77],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"customize.toml","OTHER","其他",1667,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fbmad-domain-research\u002Fcustomize.toml",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"domain-steps\u002Fstep-01-init.md","REFERENCE","参考文档",5394,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fbmad-domain-research\u002Fdomain-steps\u002Fstep-01-init.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"domain-steps\u002Fstep-02-domain-analysis.md",8640,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fbmad-domain-research\u002Fdomain-steps\u002Fstep-02-domain-analysis.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"domain-steps\u002Fstep-03-competitive-landscape.md",9525,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fbmad-domain-research\u002Fdomain-steps\u002Fstep-03-competitive-landscape.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"domain-steps\u002Fstep-04-regulatory-focus.md",6967,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fbmad-domain-research\u002Fdomain-steps\u002Fstep-04-regulatory-focus.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"domain-steps\u002Fstep-05-technical-trends.md",7506,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fbmad-domain-research\u002Fdomain-steps\u002Fstep-05-technical-trends.md",{"path":74,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":75,"sourceHtmlUrl":76},"domain-steps\u002Fstep-06-research-synthesis.md",17221,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fbmad-domain-research\u002Fdomain-steps\u002Fstep-06-research-synthesis.md",{"path":78,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":79,"sourceHtmlUrl":80},"research.template.md",581,"https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fbmad-domain-research\u002Fresearch.template.md",[82,88,95,102,109,116],{"skillNo":83,"name":84,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M76P89DWEDZ1JG6DSCQQPRPN","speclite-dev-story","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fsource-integrity\u002Flocal-source-snapshot-unverified\u002Finput\u002Fsource\u002Fcore-skills\u002Fspeclite-dev-story\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M76P87XBP3W1CZY0AJWPFSGE","speclite-code-review-01-reviewer","Fixture-owned installed skill entry for the minimal artifact loop.","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fskill-artifact-loop\u002Finput\u002F.claude\u002Fskills\u002Fspeclite-code-review-01-reviewer\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M76P8507WMXJVZ17BFKADNWV","speclite-skill-lint","只读检查 Skill 定义；用于 lint skill、check skill、检查技能或评估 Skill 规范。区分基础格式、Codex 适配和 SpecLite 约定，报告证据及未检查项；Agent 定义包转交 speclite-agent-lint。","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsupport-skills\u002Fspeclite-skill-lint\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M76P82YCP8G07G0DFBB6VZGE","speclite-skill-creator","创建或迭代 SpecLite workflow Skill；用于 create skill、新建技能、生成技能包或封装工作流。设计入口、辅助资源和验证用例；Agent 定义包转交 speclite-agent-creator。","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsupport-skills\u002Fspeclite-skill-creator\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M76P7ZVEPVECYC258WNSD9XC","speclite-html-ppt-generator","生成 SpecLite-owned 单文件 HTML PPT。用于用户要求创建 docs presentation、HTML PPT、网页 slides、Swiss Style deck、杂志风 deck，或其他可直接浏览器打开的介绍\u002F分享型 deck。核心能力：使用本 Skill 内置模板、主题、layout 和 validator 生成横向翻页 HTML，并避免依赖外部个人 skill 路径。","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsupport-skills\u002Fspeclite-html-ppt-generator\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M76P7WQ9NZDFZ306HKP8J6QX","speclite-docs-intro-ppt-creator","生成 SpecLite docs 下的介绍型 HTML PPT。用于用户要求把某个项目体系、系统设计、治理机制、理念或工作流总结成 docs presentation、HTML PPT、网页 slides、介绍 deck。核心能力：限定输出目录、基于事实材料规划叙事、调用 speclite-html-ppt-generator 生成单 HTML deck，并用确定性检查和浏览器抽样收口。","https:\u002F\u002Fgithub.com\u002Fflanliulf\u002FSpecLite\u002Fblob\u002Fmain\u002Fassets\u002Fsource\u002Fspeclite\u002Fsupport-skills\u002Fspeclite-docs-intro-ppt-creator\u002FSKILL.md",[],[]]