Review Decision Records for rationale, alternatives, constraints, consequences, and decision criteria.
npx skills add https://github.com/novel-jp/projsight-plugin --skill review-dr
Please help me install this Agent Skill. Skill: review-dr Source: https://github.com/novel-jp/projsight-plugin/tree/main/skills/review-dr Command: npx skills add https://github.com/novel-jp/projsight-plugin --skill review-dr
This Skill reviews Decision Records for clarity, completeness, and decision quality, helping teams turn vague documentation into actionable, well-justified records.
Ask the Skill to review a specific DR or the most recent records and return a scored assessment with clear improvement suggestions.
High-intent search queries and answers about installing and using this skill.
To review a Decision Record, evaluate its context, alternatives, constraints, consequences, and decision criteria, then apply structured scoring to identify rationale gaps and generate actionable improvement recommendations for documentation quality.
Structured scoring for decision records is a quality assessment method that evaluates six dimensions including context, alternatives, constraints, consequences, and decision criteria to measure documentation completeness and decision justification.
Batch-reviewing proposed decision records involves inspecting all records, detecting and excluding out-of-scope design documents, then returning scored assessments with concrete improvement suggestions for each valid decision record.
Yes, you can inspect recent decision records to evaluate their quality by applying structured scoring across six dimensions to identify gaps in rationale, alternatives, and constraints without reviewing the entire repository.
A decision record should include clear context, evaluated alternatives, documented constraints, identified consequences, and explicit decision criteria to pass a quality assessment and receive high scores across all six dimensions.
Automated decision record review should not be applied to design documents that belong outside decision workflows, as the process specifically detects and excludes out-of-scope design documentation to maintain focus on architecture and process decisions.
emcconnellDocument Architecture Decision Records with context, alternatives, and consequences.
abdullah1854Generate Markdown ADRs with sections and auto-assigned numbers from structured inputs.
AnthonyCongHieuStandardize architecture decisions with ADR templates and trade-off guidance.
Science-DiscoveryEvaluate scientific claims and evidence quality using GRADE/ROB frameworks.
