Aidd Loop

Name: Aidd Loop
Author: GrinRus

ASecurity

Loop-mode discipline for implement/review/qa (packs, scope, no questions).

5 stars
0 votes
0 copies
2 views
Added February 9, 2026

businessgo

Security analysis

A100/100

Scanned February 10, 2026

npx -y skills add GrinRus/ai_driven_dev --skill aidd-loop --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Aidd Loop?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/grinrus-aidd-loop/badge)](https://www.skillsdirectory.com/skills/grinrus-aidd-loop)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: aidd-loop
description: Loop-mode discipline for implement/review/qa (packs, scope, no questions).
lang: en
model: inherit
user-invocable: false
---

Follow `feature-dev-aidd:aidd-core` for output contract and DocOps.

## Loop discipline
1. Read order: loop pack -> review pack (if any) -> fix_plan.json when verdict=REVISE -> rolling context pack.
2. Excerpt-first: do not read full PRD/plan/tasklist/spec when the loop pack excerpt covers Goal/DoD/Boundaries/Expected paths/Size budget/Tests/Acceptance.
3. No questions in loop-mode; record blockers/handoff instead.
4. REVISE: reuse the same scope, follow fix_plan.json, and do not widen boundaries.
5. Scope guard: out-of-scope -> WARN + handoff; forbidden -> BLOCKED. Never expand boundaries yourself.
6. Tests: follow loop pack or reviewer policy; do not invent new test requirements.
7. No large logs/diffs in chat; link to `aidd/reports/**`.