md-reviewlisted

# MD Review — Scenario-Aware Markdown Review Reviews ONE Markdown document per invocation with scenario-aware weighted scoring. **Core positioning: find bugs and logic errors that would break downstream implementation first, then check whether the document's scenario-specific required content is complete.** ## Scenarios The scenario is optional. Without one, the review runs in generic mode (the scenario-completeness dimension is skipped). | Scenario | Document | Required-content focus | |---|---|---| | `prd` | Product Requirements Document | requirement list, user stories, acceptance criteria, 5W1H | | `adr` | Architecture Decision Record | context / decision / rationale / alternatives / consequences | | `add` | Architecture Design Description | architecture views, quality attributes, interfaces, data flow | | `api` | API Document | endpoint contracts, error codes, auth, runnable examples | | `brd` | Business Requirements Document | business goals, ROI, cost/revenue model, 5W1H | | `mrd` | Market Requirements Document | market analysis, user personas, value proposition, 5W1H | | `fsd` | Functional Specification Document | functional behavior, use cases, test cases, acceptance criteria | | `gdd` | Game Design Document | core loop, numbers, test cases, task lists | | `gdo` | Game Overview Document | executive summary, core concept, design pillars, USP | | `tdd` | Technical Design Document | system architecture, tech stack, coding standards, performance goals | | `ldd` | Lev