acceptance-criteria

Name: acceptance-criteria
Availability: InStock
Author: haru-llc

Document acceptance criteria for project deliverables with verification methods.

Updated Nov 21, 2025

Search Tags:#planning #documentation #verification #criteria #project-management #acceptance

Ready to run

npx skills add https://github.com/HaRu-LLC/ai-pm_system_notebooklmuse --skill acceptance-criteria-haru-llc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acceptance-criteria
Source: https://github.com/HaRu-LLC/ai-pm_system_notebooklmuse/tree/main/.agent/skills/pm/planning/acceptance-criteria
Command: npx skills add https://github.com/HaRu-LLC/ai-pm_system_notebooklmuse --skill acceptance-criteria-haru-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams explicitly define acceptance criteria for project deliverables, ensuring alignment and measurable completion.

Core Features & Use Cases

Structured criteria: Define functional, non-functional, and documentation requirements that must be satisfied for project artifacts.
Traceability: Links criteria to project artifacts and verification methods for auditability.
Use Case: When finishing a deliverable, run this to generate a formal Acceptance Criteria document stored at workspace/{ProjectName}/docs/AcceptanceCriteria.md.

Quick Start

Ask the AI to generate an acceptance criteria document for your current deliverable, including scope, success metrics, and verification steps.

Frequently Asked Questions about acceptance-criteria

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

FAQPage Schema

How do I define acceptance criteria for project deliverables?▼

Acceptance criteria definition involves identifying functional, non-functional, and documentation requirements that establish measurable validation conditions for project artifacts. This ensures alignment and objective completion tracking for every deliverable.

What is the best way to ensure traceability for verification methods in project management?▼

Ensuring traceability requires linking acceptance criteria directly to project artifacts and their corresponding verification methods. This creates an auditable path connecting scope items to specific completion conditions.

How do I generate an AcceptanceCriteria.md document for my project scope?▼

Generating an AcceptanceCriteria.md document requires applying criteria definition to your planning scope items, which saves the formalized functional and non-functional requirements to workspace/{ProjectName}/docs/. This outputs a structured markdown file.

When do I need formal acceptance criteria documentation?▼

Formal acceptance criteria documentation is necessary when finishing a deliverable and requiring measurable validation. It is applied during the planning scope phase to enforce traceability before verification begins.

Can I use this approach for non-functional requirements and documentation requirements?▼

Yes, this approach satisfies criteria for functional, non-functional, and documentation requirements. It systematically identifies and documents the specific completion conditions needed for all categories of project artifacts.

What should be included in deliverable acceptance criteria?▼

Deliverable acceptance criteria must include the project scope, success metrics, and verification steps. It explicitly defines functional, non-functional, and documentation requirements to ensure measurable completion and auditability.