phase-progress-auditor

Audit phase workflows to detect gaps between specs, plans, and code before acting.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/sarimofficial/HackathonlPhase-IV-AI-Powered-Kubernetes-Deployment-Minikube-Helm-kubectl-ai-Kagent-Gordon --skill phase-progress-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-progress-auditor
Source: https://github.com/sarimofficial/HackathonlPhase-IV-AI-Powered-Kubernetes-Deployment-Minikube-Helm-kubectl-ai-Kagent-Gordon/tree/main/.claude/skills/phase-progress-auditor
Command: npx skills add https://github.com/sarimofficial/HackathonlPhase-IV-AI-Powered-Kubernetes-Deployment-Minikube-Helm-kubectl-ai-Kagent-Gordon --skill phase-progress-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures Claude verifies the current project state (specs, plans, tasks, and implementations) before taking phase-level action, preventing unnecessary regeneration and misaligned outputs.

Core Features & Use Cases

  • Audit-before-action across phase workflows to confirm readiness
  • Detect complete, partial, missing, or inconsistent states and surface gaps
  • Propose exact next steps and generate only missing specifications or steps
  • Non-destructive guidance that preserves correct work and offers safe improvements

Quick Start

Activate phase-progress-auditor before starting a phase workflow to obtain the current state, detected issues, and recommended actions.

Frequently Asked Questions about phase-progress-auditor

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

FAQPage Schema
How do I audit project specs and code to prevent unnecessary regeneration?

Phase-level workflow auditing detects complete, partial, missing, or inconsistent states across project specs, plans, and code. It outputs the current state, detected issues, and proposed next actions to guide safe, non-destructive corrective steps.

What is the best way to detect gaps between project plans and existing code?

Detect gaps by executing an audit-before-action workflow that compares specs, plans, and code. This identifies missing or inconsistent project components and proposes exact next steps to generate only the absent specifications safely.

Why does my phase workflow generate duplicate or misaligned project outputs?

Phase workflows generate misaligned outputs when failing to verify project state before action. Auditing specs, plans, and tasks beforehand detects incomplete or inconsistent states, ensuring regeneration only targets missing specifications safely.

Can I audit project state without destroying existing correct code implementations?

Yes, you can audit project state non-destructively. This approach preserves correct work by identifying complete, partial, or missing states and offering safe improvements rather than overwriting existing implementations during regeneration.

Do I need to audit specs before starting phase-level project workflows?

Yes, you need to audit specs before starting phase-level workflows to confirm readiness. This verifies the current project state, detects gaps between plans and code, and proposes exact next actions to prevent unnecessary regeneration.