skills.rest
meriley
merileyCOMMUNITY
Explore all skills by this author →
GitHub

reviewing-design-docs

Audit RMS Backend Design Documents for completeness and approval readiness.

Updated Aug 27, 2026
Search Tags:#quality assurance#documentation#checklist#backend#design review#rms
One-click install
npx skills add https://github.com/meriley/claude-code-skills --skill reviewing-design-docs-meriley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewing-design-docs
Source: https://github.com/meriley/claude-code-skills/tree/main/skills/reviewing-design-docs
Command: npx skills add https://github.com/meriley/claude-code-skills --skill reviewing-design-docs-meriley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill systematically audits RMS Backend Design Documents, identifying gaps, blockers, and anti-patterns before formal review, saving reviewer time and improving document quality.

Core Features & Use Cases

  • Comprehensive Checklist: Validates all required sections of a design doc, from Problem Statement to Launch Plan.
  • Blocker Identification: Flags critical issues that prevent approval.
  • Use Case: Before submitting a new feature design doc for review, use this Skill to ensure it adheres to all team standards and requirements, catching potential issues early.

Quick Start

Use the reviewing-design-docs skill to check the design document located at '/path/to/design_doc.md'.

Frequently Asked Questions about reviewing-design-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a backend design doc for completeness before formal approval?▼

Reviewing a backend design doc for completeness involves validating critical sections like Problem Statement, APIs, Data Storage, Failure Modes, and Launch Plan against established team templates to surface blockers and gaps early.

What sections are required in an RMS backend design document?▼

Required sections in an RMS backend design document include the Problem Statement, APIs, Data Storage, RMS Questionnaire, Failure Modes, and Launch Plan, ensuring all standards and requirements are met before submission.

How do I identify blockers and anti-patterns in a software design review?▼

Identifying blockers and anti-patterns in a software design review requires systematically auditing the document against established patterns to flag critical issues preventing approval and catching gaps before the formal review.

Can I use a checklist to validate approval readiness for backend architecture documents?▼

You can use a comprehensive checklist to validate approval readiness for backend architecture documents by checking correctness and completeness across required sections like APIs and Data Storage.

When do I need to run a design doc audit during the software development lifecycle?▼

You need to run a design doc audit before submitting a new feature design document for review, ensuring it adheres to team standards and catching potential issues early in the software development lifecycle.

Related Skills

Explore More Software Engineering Skills→
sunholo-datasunholo-data
33

Design Doc Creator

Generate structured design documents with templates and version detection.

Official
Basic
xlelibertyxleliberty

brainstorming

Transform conceptual ideas into formal design specifications through iterative dialogue and visual prototyping.

Community
Advanced
saitarrunsaitarrun
4

documentation

Create structured technical documentation aligned with team standards and SDLC workflows.

Community
Intermediate
EmergenceAIEmergenceAI
2

validate-plan

Validate implementation plans against success criteria and architectural standards.

Official
Advanced