project-completion-audit

Audit project deliverables against acceptance criteria and operational requirements.

9|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/diegoscarabelli/system2 --skill project-completion-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-completion-audit
Source: https://github.com/diegoscarabelli/system2/tree/main/src/server/agents/skills/project-completion-audit
Command: npx skills add https://github.com/diegoscarabelli/system2 --skill project-completion-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common failure mode of declaring a project complete based on superficial impressions rather than verified, concrete evidence of deliverables.

Core Features & Use Cases

  • Epistemic Verification: Guides the agent through a checklist to ensure deliverables are real, not just theoretical.
  • Acceptance Criteria Validation: Forces a direct comparison between task requirements and actual system state or artifacts.
  • Use Case: Before signaling to the Guide that a data pipeline project is finished, run this audit to confirm row counts, schema correctness, and documentation completeness.

Quick Start

Run the project completion audit to verify that all current project tasks meet the required acceptance criteria and are ready for final review.

Frequently Asked Questions about project-completion-audit

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

FAQPage Schema
How do I verify data pipeline deliverables meet acceptance criteria before project sign-off?

Verifying data pipeline deliverables before project sign-off requires a comprehensive self-audit that evaluates row counts, schema correctness, and documentation completeness against defined acceptance criteria. This process validates that all artifacts are observable and correctly configured within the target environment.

What is epistemic verification in project quality assurance?

Epistemic verification in project quality assurance is a checklist-driven process that ensures deliverables are real and concrete rather than theoretical. It forces a direct comparison between task requirements and the actual system state to prevent declaring projects complete based on superficial impressions.

How do I audit kanban task status and documentation state for a completed project?

Auditing kanban task status and documentation state involves performing a comprehensive self-audit of project deliverables to ensure they meet operational requirements. This validates that all artifacts are verified, observable, and correctly configured within the target environment before final review.

Can I use a self-audit checklist for data engineering project completion validation?

Yes, a self-audit checklist for data engineering project completion validation guides you through verifying that deliverables meet defined acceptance criteria. It evaluates the integrity of data pipelines, kanban task status, and documentation state before final project sign-off.

What's the best way to prevent declaring a project complete without verified evidence?

Preventing premature project completion declarations requires rigorous self-audits that validate deliverables against defined acceptance criteria and operational requirements. This ensures all artifacts are verified and correctly configured, replacing superficial impressions with concrete evidence.

When do I need to run a project completion audit?

You need to run a project completion audit before signaling that a data pipeline or software engineering project is finished. It confirms that all current project tasks meet required acceptance criteria and are ready for final review by validating artifact observability and configuration.