open-fdd

Use to evaluate architecture, design proposals, refactors, module boundaries, dependency direction, data flow, concurrency model, and maintainability tradeoffs across any codebase.

Use for structured research on an unfamiliar or complex codebase before planning, reviewing, or editing. Delegates mapping, ownership, dependency, test, and risk discovery to focused subagents and returns an evidence-led research brief.

Use when implementation or review depends on external documentation, standards, protocols, APIs, SDKs, changelogs, or version-specific behavior. Produces a concise source dossier and implementation implications.

Use for rigorous pull request, branch, patch, or diff review. Runs focused review subagents for correctness, security/reliability, tests, docs/API behavior, and release risk, then synthesizes actionable findings.

Use to design, run, or review performance work with reproducible A/B baselines. Delegates benchmark inventory, profiling, correctness guardrails, and result interpretation to subagents.

Use before merging, shipping, publishing, or handing off work. Runs subagents for verification, regression risk, operational readiness, docs, compatibility, and unresolved follow-ups.

Use to compare any codebase against a specification, API contract, protocol, policy, RFC, security baseline, or product requirements document. Builds a traceability matrix and prioritizes compliance gaps.