skills.rest
zoraxl
zoraxlCOMMUNITY
Explore all skills by this author →
GitHub

evaluate

Verify software implementation against acceptance criteria from plan files.

3|Updated Apr 27, 2026
Search Tags:#workflow#quality assurance#implementation#audit#acceptance criteria#lifecycle
One-click install
npx skills add https://github.com/zoraxl/team-brain --skill evaluate-zoraxl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evaluate
Source: https://github.com/zoraxl/team-brain/tree/main/.cursor/skills/evaluate
Command: npx skills add https://github.com/zoraxl/team-brain --skill evaluate-zoraxl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of implementation drift by verifying that code changes accurately reflect the agreed-upon acceptance criteria in a development plan before a pull request is opened.

Core Features & Use Cases

  • Acceptance Criteria Audit: Maps specific plan requirements to code, tests, and configuration to identify gaps.
  • Lifecycle Management: Automatically updates phase status to implemented-pending-pr when criteria are met.
  • Use Case: Use this after finishing a coding task to ensure you haven't missed any requirements or introduced silent drift before submitting your work for review.

Quick Start

Ask the agent to evaluate the implementation for the current feature plan to verify all acceptance criteria are satisfied.

Frequently Asked Questions about evaluate

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

FAQPage Schema
How do I verify implementation matches acceptance criteria before opening a pull request?▼

To verify implementation matches acceptance criteria, scan your plan files and cross-reference defined requirements against the actual code, tests, and configuration in your repository. This identifies missing or partial gaps before code review.

What is implementation drift and how do I audit code against a feature plan?▼

Implementation drift occurs when code changes no longer reflect the agreed-upon plan. You audit code by mapping specific plan requirements directly to your repository's code and tests to identify gaps and ensure lifecycle state consistency.

When should I run an acceptance criteria audit in my development workflow?▼

You should run an acceptance criteria audit immediately after finishing a coding task. This ensures you have not missed any requirements or introduced silent drift before submitting your work for formal code review.

How does automated lifecycle management update phase status after criteria are met?▼

Automated lifecycle management updates phase status by scanning your implementation. When all defined acceptance criteria are satisfied, it automatically updates the development phase status to implemented-pending-pr.

Can I use this to identify partial implementation gaps in my code?▼

Yes, you can identify partial implementation gaps by cross-referencing plan files against your current code and configuration. It ensures lifecycle state consistency and highlights missing requirements before code review.

Related Skills

Explore More Software Engineering Skills→
jaisonerickjaisonerick

write-test-specs

Generate end-to-end QA spec files and an index mapping tests to validation criteria.

Community
Intermediate
alexandrbasisalexandrbasis
12

finisher

Commit pending changes, push to the PR branch, wait for CI, and merge the pull request.

Community
Advanced
gkganesh12gkganesh12
1

gk-review

Audit source code against documentation and test suites for architectural drift.

Community
Advanced
agent-shagent-sh
951

drift-analysis

Identify and summarize plan, documentation, issue, and scope drift in software projects.

Official
Advanced