rule-of-five

Refine an artifact through five structured passes: Draft, Correctness, Clarity, Edge Cases, and Excellence.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/naramore/dotai --skill rule-of-five
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rule-of-five
Source: https://github.com/naramore/dotai/tree/main/claude/skills/rule-of-five
Command: npx skills add https://github.com/naramore/dotai --skill rule-of-five

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterative refinement helps teams produce higher-quality outputs by methodically improving a draft through focused passes.

Core Features & Use Cases

  • Structured five-pass workflow: Draft (Pass 0) followed by Correctness, Clarity, Edge Cases, and Excellence passes, all applied to the same artifact.
  • Versatile applicability: Useful for code, design docs, RFCs, and non-trivial documentation that benefits from staged scrutiny.
  • Guided review rhythm: Clear focus per pass ensures systematic improvements without re-litigating earlier decisions.

Quick Start

Start with a draft of your artifact, then perform four single-lens refinement passes—Correctness, Clarity, Edge Cases, and Excellence—on the same work.

Frequently Asked Questions about rule-of-five

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

FAQPage Schema
How do I iteratively refine a draft document through multiple review passes?

Iterative refinement is performed through a structured five-pass workflow that applies Correctness, Clarity, Edge Cases, and Excellence passes to a draft, systematically improving a single artifact while preserving context.

What is multi-pass refinement and how does it improve code quality?

Multi-pass refinement is a staged scrutiny process that improves code quality by applying focused review lenses—Correctness, Clarity, Edge Cases, and Excellence—sequentially to the same artifact without re-litigating earlier decisions.

Can I use a structured peer-review process for technical design docs and RFCs?

Yes, a structured peer-review process works for technical design docs and RFCs by applying staged refinement passes that evaluate Correctness, Clarity, Edge Cases, and Excellence to elevate non-trivial documentation quality.

What's the best way to review edge cases without losing the original document context?

The best way to review edge cases without losing context is using a guided review rhythm with a dedicated Edge Cases pass, ensuring systematic improvements are made while preserving the artifact's surrounding context.

Does this refinement workflow require any external dependencies or specific code-review tools?

No, this refinement workflow requires no external dependencies or specific code-review tools, as it operates as a standalone multi-pass process applicable directly to code, prose, designs, and RFCs.