capability-verify-done

Validates pull requests against Definition of Done criteria and project adoption files.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/learnn-com/engineering-kb --skill capability-verify-done-learnn-com
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capability-verify-done
Source: https://github.com/learnn-com/engineering-kb/tree/main/.skills/capability-verify-done
Command: npx skills add https://github.com/learnn-com/engineering-kb --skill capability-verify-done-learnn-com

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often merge work without systematically checking Definition of Done criteria, leading to missed tests, undocumented changes, or architecture decisions lacking ADRs. This Skill automates that verification against both universal quality standards and project-specific adoption files. ## Core Features & Use Cases - Multi-area DoD checking: Evaluates requirements, code standards, architecture/ADR compliance, testing, security, performance, documentation, and manual test reports in one structured report. - Scoped and story-aware validation: Limit checks to specific areas via a scope argument, or load story acceptance criteria from a PM tool to verify requirement coverage. - Composable review workflow: Runs standalone or as Phase 4 of a /process-review pipeline, propagating HALT conditions such as missing ADRs. - Use Case: Before merging a feature PR, run the checker to confirm tests exist for new modules, no hardcoded secrets were introduced, documentation is updated, and architectural changes have a recorded ADR. ## Quick Start Ask the AI to run a Definition of Done check on the current pull request, optionally specifying a scope like testing or a story ID for acceptance criteria.

Frequently Asked Questions about capability-verify-done

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

FAQPage Schema
How do I check Definition of Done criteria on a pull request?▼

Invoke the checker on the current PR to evaluate requirements, code standards, architecture, testing, security, performance, and documentation. It reads the universal DoD checklist and project adoption files, then reports PASS, FAIL, or SKIPPED per area.

How to verify story acceptance criteria before merging code?▼

Pass a story ID so the checker loads acceptance criteria from your PM tool and evaluates whether the current code satisfies each one. Unmet criteria are reported; without a story ID, only universal DoD criteria are checked.

Can I limit the DoD check to only testing or security?▼

Yes, use the scope argument with values like testing, security, requirements, or documentation to filter the checklist to specific criterion groups. The default scope of all runs every criterion group in order.

What happens when an architectural change has no ADR?▼

A missing ADR for architectural changes is treated as a HALT condition that propagates to the composing /process-review skill. The checker itself does not create ADRs; that responsibility belongs to the decision-recording workflow.

Does the DoD checker modify code or run manual tests?▼

No, it is strictly read-only and never modifies files. For manual testing it only checks whether an existing PASS report exists for the current version; it does not execute the test suite.