aidd-loop

Coordinate implement, review, and qa loop stages with bounded scope and policy-driven retries.

5|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/GrinRus/ai_driven_dev --skill aidd-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidd-loop
Source: https://github.com/GrinRus/ai_driven_dev/tree/main/skills/aidd-loop
Command: npx skills add https://github.com/GrinRus/ai_driven_dev --skill aidd-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Loop-based development requires strict coordination across multiple stages to prevent scope creep and unbounded retries. This skill enforces disciplined loop-mode workflows for implement, review, and qa by applying bounded boundaries, roll-up of artifacts, and policy-driven retry behavior.

Core Features & Use Cases

  • Enforces loop-mode discipline for implement, review, and qa, ensuring bounded scope and deterministic progression.
  • Generates preflight artifacts (readmap, writemap, loop pack) to drive stage execution and handoffs.
  • Integrates with canonical run-time entrypoints (loop_pack, loop_run, loop_step) to coordinate iterations, retries, and policy-driven outcomes.

Quick Start

Run the aidd-loop workflow for a ticket to start a bounded loop cycle.

Frequently Asked Questions about aidd-loop

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

FAQPage Schema
How do I enforce bounded scope during loop-mode development across implement, review, and qa stages?

Loop-mode development enforces bounded scope by applying policy-driven retries and roll-up of artifacts across implement, review, and qa stages. This ensures deterministic progression and prevents scope creep in complex multi-stage projects.

What are preflight artifacts in automated loop iteration workflows?

Preflight artifacts are generated readmaps, writemaps, and loop packs that drive stage execution and handoffs. They coordinate iterations and policy-driven outcomes through canonical run-time entrypoints like loop_pack, loop_run, and loop_step.

How do I prevent unbounded retries in automated development loop coordination?

Automated development loop coordination prevents unbounded retries by enforcing policy-driven retry behavior. Bounded boundaries and artifact generation ensure deterministic progress across implement, review, and qa stages.

Can I use loop pack generation to coordinate stage handoffs in complex multi-stage projects?

Loop pack generation coordinates stage handoffs in complex multi-stage projects by producing preflight artifacts. These artifacts drive stage execution through canonical run-time entrypoints, ensuring bounded scope and deterministic progression.

Does policy-driven loop execution work without external dependencies?

Policy-driven loop execution works without external dependencies by using internal preflight artifacts and canonical run-time entrypoints. It enforces bounded boundaries and deterministic progression autonomously across development stages.

When should I not use automated loop discipline for development coordination?

Automated loop discipline should not be used when strict bounded scope and preflight artifact generation are unnecessary. Projects requiring flexible, unbounded iterations without policy-driven retry constraints will find the loop-mode workflow restrictive.