Review design documents, RFCs, and ADRs for completeness and readiness.
npx skills add https://github.com/Arafly/sre-playbooks --skill design-review-adr
Please help me install this Agent Skill. Skill: design-review-adr Source: https://github.com/Arafly/sre-playbooks/tree/main/design-review-adr Command: npx skills add https://github.com/Arafly/sre-playbooks --skill design-review-adr
This Skill helps you review, write, and improve design documents, RFCs, architecture decision records, and technical proposals so they are clear, testable, and implementation-ready. It is designed to expose missing context, weak assumptions, and risky decisions before they become costly mistakes.
Ask me to review your design document, RFC, or ADR and identify blocking gaps, missing alternatives, and implementation-readiness issues.
High-intent search queries and answers about installing and using this skill.
Reviewing an architecture decision record requires checking it for completeness in risk analysis, trade-off evaluation, reversibility, observability, and ownership to ensure the technical proposal is clear and implementation-ready.
An RFC or technical proposal must include clear context, trade-off analysis, rollback plans, unresolved questions, and alternatives. A design review validates these elements to expose missing context and weak assumptions before implementation.
You need to write an architecture decision record for a system change when technical decisions require clear context, constraints, and trade-off analysis for future readers to understand the outcome without hidden context.
Identifying blocking gaps in a migration design document involves critiquing the draft for weak assumptions, missing alternatives, and risky decisions, validating that operational readiness, rollback plans, and observability are fully addressed.
Yes, the design review process applies to both authoring and critique workflows for RFCs and technical proposals, strengthening documents by exposing missing context and validating implementation details for system changes.
Validating operational readiness in a technical proposal requires checking that the document explicitly includes implementation details, rollback plans, observability metrics, ownership assignment, and documented unresolved questions.
Sir-chawakornGenerate structured engineering RFCs with standardized sections for motivation, architecture, and tradeoffs.
pingmepiGenerate a Technical Requirements Document from an approved product definition pipeline.
mhylleReview code changes for architectural conformance and quality gates.
jagreehalDocument architecture decisions and trade-offs using ADR patterns.
