agentleFS
Sign inStart free
xiaolaixiaolai/vmark/.claude/skills/plan-audit/SKILL.md

plan-audit

Skill851 starsChanged 29 days agoISCView on GitHub

Audit an implementation against a plan (dev-docs/plans/*). Use when a user asks to check for gaps, logic errors, or missing tests relative to a plan or Work Items.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If unclear, ask for the plan path or the WI list.

    line 16
  2. Very specific:

    Use git log, git show --stat, rg, and file inspection.

    line 26
  3. Distinctive:

    Check each acceptance item vs actual behavior.

    line 30
  4. Distinctive:

    If the plan references specs, verify implementation matches those specs.

    line 33
  5. Distinctive:

    If the plan is missing acceptance/tests, record it as a plan-quality gap.

    line 34
  6. Distinctive:

    Do not run tests here unless the user explicitly asks.

    line 60
  7. Distinctive:

    If you cannot locate the plan, stop and ask for it.

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Plan Audit

Overview

Audits completed work against a plan (WIs + acceptance + tests) and reports gaps, logic errors, and missing coverage with file/line references.

Workflow (Audit)

  1. Locate the plan
    • Prefer dev-docs/plans/<plan>.md.
    • If unclear, ask for the plan path or the WI list.
  2. Extract audit checklist
    • For each WI, list:
      • Goal
      • Acceptance criteria
      • Tests required
      • Touched areas (files/symbols)
  3. Map implementation to WIs
    • Use git log, git show --stat, rg, and file inspection.
    • Record which files/commits satisfy each WI.
  4. Gap & correctness analysis
    • Check each acceptance item vs actual behavior.
    • Find logic errors, edge-case failures, and incomplete flows.
    • Validate test coverage against the “Tests (first)” section.
    • If the plan references specs, verify implementation matches those specs.
    • If the plan is missing acceptance/tests, record it as a plan-quality gap.
  5. Report findings
    • Order by severity: Critical → High → Medium → Low.
    • Each finding must include:
      • WI reference
      • File path + line
      • Why it violates the plan
      • Expected behavior per plan

Output Format (required)

  • Findings (ordered by severity)
    • File:line and WI reference
    • Impact and suggested fix
  • Plan Gaps Summary
    • WI‑### → missing/partial acceptance items
  • Test Coverage Gaps
    • Missing tests, broken tests, or “test not written”
  • Notes / Risks
    • Any assumptions or unverified areas
  • Evidence
    • Cite concrete evidence for each finding (files/lines/commit IDs).

Audit Rules

  • Do not run tests here unless the user explicitly asks; this is an inspection pass.
  • Be strict about spec drift: if behavior diverges from plan text, flag it.
  • If you cannot locate the plan, stop and ask for it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free