ワンクリックで
bmad-market-research
Conduct market research on competition and customers. Use when the user says they need market research
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Conduct market research on competition and customers. Use when the user says they need market research
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
One iteration of an unattended development loop. Use when invoked by name.
Distill any intent input into the SPEC kernel + companions — the canonical, preservation-validated machine contract for downstream work. Use when the user says "create a spec", "distill this into a spec", "validate this spec", "update the spec", or "break this into stories".
Adversarial code review using parallel review layers and structured triage. Use when the user says "run code review" or "review this code"
Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.
Review a code change for changed behavior that could regress without reliable verification catching it. Use when checking whether a change is adequately verified.
Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.
| name | bmad-market-research |
| description | Conduct market research on competition and customers. Use when the user says they need market research |
Goal: Conduct comprehensive market research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
Your Role: You are a market 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.
steps/step-01-init.md) resolve from the skill root.{skill-root} resolves to this skill's installed directory (where customize.toml lives).{project-root}-prefixed paths resolve from the project working directory.{skill-name} resolves to the skill directory's basename.⛔ Web search required. If unavailable, abort and tell the user.
Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow
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:
{skill-root}/customize.toml — defaults{project-root}/_bmad/custom/{skill-name}.toml — team overrides{project-root}/_bmad/custom/{skill-name}.user.toml — personal overridesAny 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.
Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.
Treat 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.
Load config from {project-root}/_bmad/bmm/config.yaml and resolve:
{user_name} for greeting{communication_language} for all communications{document_output_language} for output documents{planning_artifacts} for output location and artifact scanning{project_knowledge} for additional context scanningGreet {user_name}, speaking in {communication_language}.
Execute each entry in {workflow.activation_steps_append} in order.
Activation is complete. If activation_steps_prepend or activation_steps_append were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
"Welcome {{user_name}}! Let's get started with your market research.
What topic, problem, or area do you want to research?
For example:
Based on the user's topic, briefly clarify:
After gathering the topic and goals:
research_type = "market"research_topic = [discovered topic from discussion]research_goals = [discovered goals from discussion]research_topic_slug from {{research_topic}}: lowercase, trim, replace whitespace with -, strip path separators (/, \), .., and any character that is not alphanumeric, -, or _. Collapse repeated - and strip leading/trailing -. If the result is empty, use untitled.{planning_artifacts}/research/market-{{research_topic_slug}}-research-{{date}}.md with exact copy of the ./research.template.md contents./steps/step-01-init.md with topic contextNote: 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 market research.
✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config {communication_language}