bmad-technical-research

Conducts multi-step web-verified technical research and generates cited research reports.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-technical-research-asygnuz-s-a-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-technical-research
Source: https://github.com/Asygnuz-S-A-S/one-star/tree/main/.claude/skills/bmad-technical-research
Command: npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-technical-research-asygnuz-s-a-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Producing a trustworthy technical research report requires gathering current web data, verifying sources, and structuring findings across architecture, integration, and implementation topics, which is slow and error-prone when done manually. ## Core Features & Use Cases - Guided Six-Step Workflow: Walks through scope confirmation, technology stack analysis, integration patterns, architectural patterns, implementation research, and final synthesis with user confirmation at each stage. - Web-Verified Citations: Requires live web searches for every claim, with source URLs and confidence levels recorded in the output document. - Structured Report Generation: Produces a complete Markdown research document with executive summary, table of contents, recommendations, and appendices from a reusable template. - Use Case: Ask for a technical research report comparing GraphQL and REST API architectures, and the workflow will research current sources step by step and deliver a fully cited report. ## Quick Start Ask the assistant to conduct a technical research report on a topic such as serverless deployment options for Node.js.

Frequently Asked Questions about bmad-technical-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a technical research report with cited sources?▼

Start the workflow by stating your research topic and goals. It guides you through six steps covering scope, technology stack, integration, architecture, and implementation, then synthesizes a cited Markdown report.

What topics can this technical research workflow cover?▼

It covers any technology or architecture topic, such as framework comparisons, API design patterns, cloud deployment options, or database selection. The scope is confirmed with you in the first step before research begins.

Does the technical research workflow require web search?▼

Yes, web search is a hard prerequisite. The workflow aborts if web search is unavailable, because every factual claim must be verified against current live sources rather than training data alone.

What format is the final research report output?▼

The output is a Markdown document created from a template, containing an executive summary, table of contents, sectioned analysis with source URLs, strategic recommendations, and appendices. It is saved under the planning artifacts directory.

Can I customize the research workflow behavior?▼

Yes, a customize.toml file supports activation step overrides, persistent facts loaded from project files, and an on_complete hook. Team and user-level TOML overrides merge with the defaults.