Auditing Progress

by prime-radiant-inc

Auditing Progress is a Quality skill for Claude Code, published by prime-radiant-inc in iterative-development.

179 stars17 forkson prime-radiant-inc/iterative-developmentAdded 2026/09/07+1% in starsRepository updated 2026/06/06

View source on GitHub Download repo ZIP

ai-agentsautonomous-agentsclaude-codeclaude-code-pluginmethodology

Install in seconds

Install Auditing Progress

Copy Auditing Progress into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/prime-radiant-inc/iterative-development/tree/main/skills/auditing-progress ~/.claude/skills/auditing-progress

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/prime-radiant-inc/iterative-development.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/auditing-progress/SKILL.md in prime-radiant-inc/iterative-development
Installs to: ~/.claude/skills/auditing-progress
Collection: One of 6 skills cataloged from this repository
Category: Quality — 1817 skills

What Auditing Progress does

Auditing Progress checks evidence quality after an iteration using three tiers: current stories, impacted scenarios, and sentinel regressions. Use it when you need to verify that behavior proof is durable before moving to the next iteration.

Auditing Progress is cataloged under Quality on DirSkills. Auditing Progress comes from a repository tagged ai-agents, autonomous-agents, claude-code, claude-code-plugin and methodology.

Documentation

README

Excerpt

Auditing Progress

Overview

Runs after every iteration as part of the planning cycle. Verifies behavior evidence quality in three tiers using parallel adversarial review (PAR) — two paired auditor subagents evaluate the same work in parallel with competitive framing.

The audit answers: "Does durable, reusable evidence exist at the correct seam for every externally observable behavior this iteration touched?"

When to Use

Invoked by iterative-development after every running-an-iteration call, before picking the next iteration.

Audit Process

1. Partition the audit into three tiers

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Auditing Progress

What else does prime-radiant-inc publish alongside Auditing Progress?
Auditing Progress is one of 6 skills that DirSkills catalogs from prime-radiant-inc/iterative-development, the repository it ships in. Its siblings there include Extracting Requirements, Implementing Tasks and Iterative Development. Each one is a separate skill with its own page in this directory, installs the same way Auditing Progress does, and is maintained by prime-radiant-inc in that same repository. The rest of the collection is listed on the prime-radiant-inc/iterative-development page.
How does Auditing Progress compare to other Quality skills?
Auditing Progress ranks #1677 by stars among the 1817 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Auditing Progress against them. Open each page to compare what they document and how they install.