audit-epic

Audit an epic and its child feature plans for gaps, drift, and incomplete criteria.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill audit-epic-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-epic
Source: https://github.com/pnewsam/skills/tree/main/archive/audit-epic
Command: npx skills add https://github.com/pnewsam/skills --skill audit-epic-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Epics and their child feature plans drift out of sync: checkboxes get marked without verified acceptance criteria, plans go missing, statuses contradict evidence, and orphaned plans appear. This Skill produces an evidence-backed audit of an epic's actual state so you know what is truly done and what remains. ## Core Features & Use Cases - Epic health audit: Reads an epic plan and every child feature plan, classifying gaps as unplanned, incomplete, tracking drift, status mismatch, or incomplete definition of done, then writes a dated audit report to docs/epics/. - Dependency and orphan detection: Escalates gaps that block other features and surfaces feature plans that reference the epic but are absent from its child list. - Gap-closure planning: In Closure mode, writes a prioritized punch list mapping each unresolved gap to a concrete skill or human decision while preserving completed items across reruns. - Use Case: Before shipping an epic, ask for an audit to discover that two features have unchecked must-have criteria and one feature plan is missing entirely, then generate a closure plan ordering the remaining work by dependency impact. ## Quick Start Use the audit-epic skill to assess the health of the epic in docs/epics and list its highest-severity gaps.

Frequently Asked Questions about audit-epic

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

FAQPage Schema
How do I audit an epic for incomplete work?▼

Point the skill at an epic plan under docs/epics and it reads every referenced child feature plan, checking acceptance criteria, task progress, and definition-of-done status. It writes a dated audit report classifying each gap by type and severity.

What is tracking drift in a feature plan?▼

Tracking drift occurs when task completion suggests work happened but acceptance criteria were never verified. The audit flags this because checkboxes record claimed state, not proof of working code.

Does the epic audit modify my plans or tickets?▼

No, the audit only writes its own report artifacts under docs/epics. It never modifies the epic, feature plans, source code, branches, tickets, or external systems.

How does the gap-closure plan handle reruns?▼

On rerun it reads the existing closure plan, retains completed items whose gaps remain resolved, updates evidence and severity, and marks obsolete items explicitly. Completed work is never reopened just because wording changed.

When should I use Closure mode instead of a plain audit?▼

Use Closure mode when you ask what to do next, want a punch list, or need to plan the gaps. It performs the full audit first, then writes a prioritized gap-closure plan ordered by blockers and severity.