Loading...
Loading...
Found 37 Skills
This skill should be used to refine brainstorm or plan documents before proceeding to the next workflow step. It applies when a brainstorm or plan document exists and the user wants to improve it.
Review legal documents as an experienced attorney. Analyzes contracts, ToS, privacy policies, NDAs, and corporate docs section-by-section. Identifies risks, gaps, and unfavorable terms with specific replacement text for problematic clauses.
Structural review of documents for gaps, clarity, completeness, and organization. Use when a brainstorm, plan, spec, ADR, or any doc needs polish before the next workflow step. For exploring new ideas from scratch, use brainstorming instead.
Extract structured data from multiple documents into comparison matrix with citations. Use for bulk document review.
[BETA] Stress-test an existing implementation plan and selectively strengthen weak sections with targeted research. Use when a plan needs more confidence around decisions, sequencing, system-wide impact, risks, or verification. Best for Standard or Deep plans, or high-risk topics such as auth, payments, migrations, external APIs, and security. For structural or clarity improvements, prefer document-review instead.
Use when reviewing, rewriting, or editing someone else's technical text, when writing a review report on a document, or as the final check before delivering any document. Encodes the severity mapping, the findings format, the what-not-to-flag list, and the delivery checklist. Use before any document ships, even when it looks fine.
PRD review, requirements review, check PRD quality. Use when: Review is required after PRD completion, "review PRD", "PRD review", "requirements review"
Review contracts for concerning clauses, extract key terms, compare to standard terms, and flag unusual provisions. Use when user needs contract review, legal document analysis, or agreement evaluation.
Runs one or more installed review lenses — adversarial critique, edge cases, verification gaps, structure, prose — and reports triaged findings. Use when, and only when, the user asks you to review a diff, a pull request, or an artifact — code or documents, one or many — and actually says "review"; an explicit skill:bmad-review directive from another skill counts as that ask. A request to act on feedback from an earlier review is a change, not a review. Never invoke this uninvited, including on edits you just made.
Review a spec document against codebase reality, identifying gaps and ensuring sound, robust implementations.
Analyze, draft, and review Severability clauses for General contracts. Use when the user mentions severability, savings clause, void provision, or asks to review, redline, or generate this clause type. Returns structured risk assessment, plain-language summary, and suggested alternative language.
Create, edit, comment on, and share markdown documents via Proof's web API and local bridge. Use when asked to "proof", "share a doc", "create a proof doc", "comment on a document", "suggest edits", "review in proof", or when given a proofeditor.ai URL.