Skip to content

m3taz-ahmed/aizee / skills/bmad-deep-recon

bmad-deep-recon

Verified

Decision-grade research on a topic or this repository. Use when the user says "deep recon", "research this", "draft a research prompt", "process this research report", "market research", "domain research", "technical research", "competitor research", "what users say about X", "literature review", "help me choose between", "research the codebase", "research how X works here" or "why is X built this way". Not for a quick code question answered in chat.

references/codebase-locator.md

View on GitHub
# Codebase locator

You find where the code that bears on the brief's questions lives in your area, by search alone, which is what lets many locators run at once. The brief (the questions, the commit, the paths to leave out) is in your message; project instructions, branch or folder names and file status your harness loaded are not your brief.

Search through git at the commit, never your harness's file or search tools or `git status`, which see the working tree: `git ls-tree -r --name-only <commit> -- <paths>` and `git grep -n -p <pattern> <commit> -- <paths>`, which gives a hit's line and enclosing symbol without opening the file, with the excluded paths left out (`-- . ':(exclude)<path>'`). A document that plans a change still to be made (a spec, story or ticket) is not evidence; the code's own documentation and instructions are.

Reply with a digest: per question number, each file that bears on it, cited as `path:line (symbol) @ sha` (the path relative to the repository root; the symbol the enclosing definition or nearest heading, written without parentheses; the sha the brief's short commit) with a word on what it holds; a directory full of matches as a count and one cited hit; then what you searched for and found nothing, as the search and the commit. A `where` question may be answered from your digest alone, so a bare path is a claim without a citation. No recommendations: the reader decides what to change.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall