audit-impl

Audit completed implementations against originating plans and issue GO or NO GO verdicts.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Trecek/useful-claude-skills --skill audit-impl-trecek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-impl
Source: https://github.com/Trecek/useful-claude-skills/tree/main/.claude/skills/audit-impl
Command: npx skills add https://github.com/Trecek/useful-claude-skills --skill audit-impl-trecek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit a completed implementation against its originating plan(s) and determine merge readiness, returning a GO verdict or NO GO with remediation for retry.

Core Features & Use Cases

  • Validate implementations against one or more plans, including manifest-driven multi-group pipelines
  • Produce a GO verdict for merges or a NO GO with a remediation file to retry the work
  • Provide structured findings and context to guide fast remediation

Quick Start

Run the audit on the current worktree against the active plan(s) and generate a remediation file if needed.

Frequently Asked Questions about audit-impl

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

FAQPage Schema
How do I audit implementation diffs against a plan before merging?

To audit implementation diffs against a plan before merging, this Skill compares file-level changes against originating plans and returns a GO or NO GO verdict. It gathers diffs and plan coverage to determine merge readiness automatically.

What happens when a completed implementation does not match the project plan?

When a completed implementation does not match the project plan, the audit returns a NO GO verdict and generates a remediation file. This provides structured findings and context to guide fast remediation for retrying the work.

Can I audit a standalone worktree without an active multi-group manifest?

Yes, you can audit a standalone worktree without an active multi-group manifest. The audit process supports single-plan pipelines, multi-group manifests, and standalone worktrees to evaluate merge readiness in any context.

How does plan coverage analysis work for multi-group pipelines?

Plan coverage analysis for multi-group pipelines works by using Explore subagents to gather file-level diffs across all groups. It validates the implementation against the manifest-driven plans to produce a structured GO or NO GO merge decision.

Do I need to manually create a remediation file when the merge audit fails?

No, you do not need to manually create a remediation file when the merge audit fails. The Skill automatically generates a remediation file alongside the NO GO verdict to provide structured guidance for fast retry.