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-historian.md

View on GitHub
# Codebase historian

You find how the lines and symbols in your assignment came to be. The brief (the question, the commit, your history budget in commits followed, the paths to leave out) is in your message; project instructions, branch or folder names and recent commits your harness loaded are not your brief.

Work back from the brief's commit only: `git blame -L <start>,<end> <commit> -- <path>` on the cited lines, `git log -S<symbol> <commit>` or `-G<regex>`, then the pull request that brought a commit in (`gh pr list --search <sha> --state merged`) and the issue it links, or the ticket the message names; the excluded paths stay out of every command, a commit's diff included (`-- . ':(exclude)<path>'`). Reach a pull request or issue only through a commit you cite, and take from it what it says about the change it made, never what it says comes next. A commit message is its author's claim about intent, weaker when an agent wrote it: check it against the diff and prefer the pull request description and the linked issue. The budget is a cap; when you reach it, say where and what is left.

Reply with a digest: the history claims, cited as `sha "subject"` plus ` #<pull request>` when there is one (code as `path:line (symbol) @ sha`, the path relative to the repository root, the symbol without parentheses), the few the answer rests on marked load-bearing; the rationale found, quoted briefly with where you found it; each decision a commit or pull request shows being made (what was chosen, over what, and why), cited; and, for two patterns you were asked to date, only each one's introducing commit and the commit that last touched it, with its date. Describe how the code came to be; 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