bmad-deep-recon

Drafts, runs, and processes decision-focused research reports with cited sources and verification.

Updated Sep 4, 2026
One-click install
npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-deep-recon-joao-victor-medeiros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-deep-recon
Source: https://github.com/Joao-Victor-Medeiros/save-sc/tree/main/.agents/skills/bmad-deep-recon
Command: npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-deep-recon-joao-victor-medeiros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Turning open-ended research questions into trustworthy, decision-ready findings is slow and error-prone: claims go uncited, sources go stale, and raw reports are hard for downstream planning artifacts to consume. This Skill structures the entire research lifecycle so every claim carries a source, freshness window, and verification status. ## Core Features & Use Cases - Three research modes: Draft a deep-research prompt for external tools (ChatGPT, Gemini, Perplexity), Process a finished report into a cited summary, or Run native research with parallel web-search subagents. - Typed research packs: Built-in packs for market, domain, technical, competitive, user-voice, and academic literature research, each with prioritized dimensions, freshness bars, and two-source claim classes, plus a selection mode for choosing between candidates. - Verification and staleness tracking: A claims ledger in an append-only memlog, configurable validation levels with red-team passes, and deterministic scripts for citation checks, claim tallies, and staleness computation. - Use Case: Before committing to a market entry, ask for market research; the Skill holds a plan gate, fans out researcher subagents, verifies load-bearing claims, and produces research.md plus an optional self-contained HTML briefing that PRD and brief workflows consume directly. ## Quick Start Ask the assistant to run deep recon market research on the topic and decision you are facing, for example: research the market for my product idea so I can decide whether to enter it.

Frequently Asked Questions about bmad-deep-recon

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

FAQPage Schema
How do I run deep research on a market or technology topic?▼

Invoke the skill with your topic and the decision it serves, then approve the plan gate showing dimensions, effort preset, and time estimate. Researcher subagents fan out with web search, write digests to a run folder, and the lead assembles a cited research.md report.

How do I process an existing research report into a summary?▼

Name or drop the report file and ask to process it. The skill files the original into an imports folder, extracts claims into digests with provenance, spot-checks load-bearing claims, and distills a decision-first cited summary that downstream skills read directly.

What research types does deep recon support?▼

It ships with six packs: market, domain, technical, competitive, user-voice, and academic literature. Each pack defines prioritized dimensions, source craft, freshness windows, and two-source claim classes, and custom types can be added through override TOML files.

Can I use it to choose between vendors or technologies?▼

Yes, the selection shape layers over any research type for choose-between-candidates decisions. It builds a requirements frame, screens candidates, scores finalists against weighted criteria including cost and lock-in, and delivers a decision matrix with a verdict and runner-up.

Does the research skill work without web access?▼

Run mode requires web access and the skill says so rather than fabricating research. Without it, you can still Draft a prompt for an external deep-research tool or Process a report you already have.

How are stale research claims detected and refreshed?▼

Each pack sets freshness windows per claim class, and the recon_kit staleness script computes re-check dates from the claims ledger. The Refresh intent re-verifies only stale claims and appends a delta report, flagging overturned claims that downstream artifacts consumed.