loop

Loop reviewer and lead-engineer reviews until all REQ items in spec.md pass.

2|1|Updated Mar 16, 2026

Search Tags:#requirements #verification #spec #loop #review-process #qa-cycle

Ready to run

npx skills add https://github.com/ByeongminLee/nextjs-claude-code --skill loop-byeongminlee

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: loop
Source: https://github.com/ByeongminLee/nextjs-claude-code/tree/main/template/.claude/skills/loop
Command: npx skills add https://github.com/ByeongminLee/nextjs-claude-code --skill loop-byeongminlee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Loop until all REQs in spec.md are satisfied to ensure feature readiness through iterative verification and acceptance testing during the development cycle.

Core Features & Use Cases

Automated REQ verification: Re-checks and validates that every REQ in spec.md is satisfied after each iteration.
Controlled review cycles: Orchestrates the reviewer → lead-engineer → re-review loop to converge on a green spec.
Guaranteed readiness: Ensures the feature is ready for the next development stage once all REQs are satisfied.

Quick Start

Run the loop after writing or updating spec.md to automatically iterate reviews until every REQ is satisfied.

Frequently Asked Questions about loop

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

FAQPage Schema

How do I automate spec.md requirement verification until all items pass?▼

Spec.md requirement verification is automated by running a loop that iterates through reviewer, lead-engineer, and re-review cycles. It continuously validates every REQ item until they are all satisfied, guaranteeing feature readiness for the next development stage.

What is a QA review cycle for closing requirements in a spec file?▼

A QA review cycle for requirements coordinates a reviewer, a lead-engineer, and a re-review process to close REQ items. It loops through validation checks until the spec file converges on a green state with all requirements fully satisfied.

Do I need a predefined spec.md file to start the requirement review loop?▼

Yes, you need a predefined spec.md file containing your REQ items to start the requirement review loop. The workflow requires this defined specification along with a loop agent and loop controls to re-run reviews until all requirements pass.

How to ensure feature readiness through iterative acceptance testing?▼

Feature readiness through iterative acceptance testing is ensured by looping until all REQs in spec.md are satisfied. The controlled review cycles repeatedly verify compliance, guaranteeing the feature is ready for the next development stage once all requirements pass.

What's the best way to manage a reviewer and lead-engineer re-review loop?▼

Managing a reviewer and lead-engineer re-review loop is best handled by using a loop agent with defined loop controls. This orchestrates the review sequence and automatically re-runs the cycle until all spec.md requirements achieve compliance.

When should I stop looping requirement reviews for spec compliance?▼

You should stop looping requirement reviews for spec compliance when every REQ item in spec.md is fully satisfied. The loop is designed to automatically terminate once the iterative verification confirms that all requirements have passed validation.