criteria-audit

Audit EXECUTION_PLAN.md acceptance criteria for type tags and Verify lines.

39|5|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/benjaminshoemaker/ai_coding_project_base --skill criteria-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: criteria-audit
Source: https://github.com/benjaminshoemaker/ai_coding_project_base/tree/main/.claude/skills/criteria-audit
Command: npx skills add https://github.com/benjaminshoemaker/ai_coding_project_base --skill criteria-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits EXECUTION_PLAN.md to ensure acceptance criteria are automation-ready, include verification metadata, and capture manual reasons when applicable. It is designed for use when preparing Phase 1 or after editing EXECUTION_PLAN.md.

Core Features & Use Cases

  • Validation of Type Tags: Every acceptance criterion must include a type tag such as (TEST), (CODE), (LINT), (TYPE), (BUILD), (SECURITY), or (BROWSER:DOM).
  • Verification Lines: Each criterion must include a Verify: line unless it is MANUAL, and MANUAL criteria must include a Reason: line.
  • Pre-Phase Setup Verification: All Pre-Phase Setup items must have a Verify: line; missing ones are flagged for human review.
  • Audit Output: Produces a structured report highlighting missing tags, Verify lines, manual reasons, and any Pre-Phase setup gaps.

Quick Start

  • Copy this skill into your project workspace and run it against an EXECUTION_PLAN.md path, e.g. criteria-audit /path/to/EXECUTION_PLAN.md
  • Review the generated audit report and resolve any issues before Phase 1 initiation.

Frequently Asked Questions about criteria-audit

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

FAQPage Schema
How do I verify EXECUTION_PLAN.md is ready for automated testing?

You can validate execution plan criteria by auditing the file to ensure each criterion includes a type tag like (TEST) or (CODE) and a Verify line. This structured audit flags missing verification metadata and manual reasons before Phase 1 initiation.

What type tags should acceptance criteria include for automation readiness?

Acceptance criteria should include type tags such as (TEST), (CODE), (LINT), (TYPE), (BUILD), (SECURITY), or (BROWSER:DOM). These tags classify the verification method required for each specific automation criterion.

How do I handle manual verification items in an execution plan?

For manual verification items in an execution plan, you must include a MANUAL type tag and explicitly state a Reason: line. The audit process flags any manual criteria missing this required justification metadata.

Does the execution plan audit check Pre-Phase Setup verification lines?

Yes, the execution plan audit checks Pre-Phase Setup verification lines. All Pre-Phase Setup items must have a Verify: line, and the audit report will flag any missing ones for human review before starting.

When should I run an execution plan criteria audit?

You should run an execution plan criteria audit when preparing for Phase 1 or immediately after editing EXECUTION_PLAN.md. Running it at these points ensures all acceptance criteria remain automation-ready and properly structured.