skills.rest
charly-vibes
charly-vibesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

rule-of-5-universal

Apply Steve Yegge's Rule of 5 iterative review to code, plans, and documents.

1|Updated Jan 31, 2026
Search Tags:#quality assurance#code review#documentation#iterative development#review#artifact review
One-click install
npx skills add https://github.com/charly-vibes/wai --skill rule-of-5-universal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rule-of-5-universal
Source: https://github.com/charly-vibes/wai/tree/main/.agents/skills/rule-of-5-universal
Command: npx skills add https://github.com/charly-vibes/wai --skill rule-of-5-universal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the iterative review process for any digital artifact, ensuring it progresses from a rough draft to a polished, production-ready state through structured, multi-stage feedback.

Core Features & Use Cases

  • Structured Review Stages: Guides users through five distinct phases: Draft, Correctness, Clarity, Edge Cases, and Excellence.
  • Artifact Agnostic: Applicable to code, plans, research, issues, specs, and general documents.
  • Use Case: A software engineer can use this Skill to review a new feature's design document, ensuring it's structurally sound, logically correct, clearly written, accounts for edge cases, and meets high-quality standards before implementation.

Quick Start

Apply the universal rule of 5 review to the attached document 'design-spec.md'.

Frequently Asked Questions about rule-of-5-universal

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

FAQPage Schema
How do I iteratively review a design document before implementation?▼

Iterative design document review applies a five-stage process: Draft, Correctness, Clarity, Edge Cases, and Excellence. This structured progression ensures artifacts are logically sound, clearly written, and account for edge cases before reaching production-ready quality.

What is the Rule of 5 process for code and artifact review?▼

The Rule of 5 is an iterative review process guiding artifacts through five phases: Draft, Correctness, Clarity, Edge Cases, and Excellence. Each stage has defined convergence criteria to ensure progressive refinement from rough draft to polished state.

Can I use this structured review process for research plans and specs?▼

Yes, this artifact review process is artifact-agnostic and fully applicable to research, issues, plans, and specs. It evaluates structural soundness, logical correctness, and edge case handling to meet high-quality standards across various document types.

What is the best way to refine a rough draft into a production-ready document?▼

The best way to refine a rough draft is using a multi-stage feedback loop with defined convergence criteria for each phase. Progressive refinement through Draft, Correctness, Clarity, Edge Cases, and Excellence ensures the document reaches a polished, production-ready state.

Does this artifact review method work for general documentation and issues?▼

Yes, this review method works for general documentation, code, and issues. It applies structured, multi-stage feedback across any digital artifact, verifying correctness and clarity while accounting for edge cases to ensure excellence.

Related Skills

Explore More Software Engineering Skills→
olioskarolioskar

review

Run structured code reviews on pull requests and branches with severity-ranked findings.

Community
Advanced
dfrysingerdfrysinger
36

design

Translate approved research and goals into a validated system architecture and vertical slices.

Community
Advanced
charly-vibescharly-vibes

code-review

Review code iteratively using the Rule of 5 methodology.

Community
Intermediate
rikdcrikdc
2

go-review

Review Go code for correctness, security, and performance issues.

Community
Advanced