gsd-eval-review

Audit completed AI development phases against defined evaluation specifications.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/nnexai/git-stacks --skill gsd-eval-review-nnexai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-eval-review
Source: https://github.com/nnexai/git-stacks/tree/main/.codex/skills/gsd-eval-review
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-eval-review-nnexai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the lack of visibility into whether an AI-driven development phase met its stated evaluation criteria, preventing the accumulation of technical debt and unverified code.

Core Features & Use Cases

  • Coverage Audit: Automatically verifies if the evaluation strategy defined in AI-SPEC.md was actually executed.
  • Remediation Planning: Generates a structured EVAL-REVIEW.md file containing scores, verdicts, and actionable steps to fix identified gaps.
  • Use Case: After completing a complex feature implementation, run this skill to ensure all edge cases and performance benchmarks defined in the initial specification were properly tested and validated.

Quick Start

Invoke the gsd-eval-review skill to audit the most recently completed development phase and generate a remediation plan.

Frequently Asked Questions about gsd-eval-review

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

FAQPage Schema
How do I audit AI development phases for evaluation coverage?

Audit AI development phases by retroactively comparing execution logs against defined specifications. This process identifies unverified code and technical debt by verifying if the evaluation strategy stated in AI-SPEC.md was actually executed.

How do I generate a remediation plan for untested edge cases?

Generate a remediation plan by running a retroactive evaluation audit to identify test coverage gaps. This produces a structured EVAL-REVIEW.md file containing scores, verdicts, and actionable steps to fix missing edge case validations.

What is evaluation coverage gap analysis in software engineering workflows?

Evaluation coverage gap analysis is a quality assurance process that compares completed execution logs against project-specific evaluation standards. It documents missing test coverage and unverified performance benchmarks to ensure compliance with the initial specification.

Do I need an AI-SPEC.md file to run an evaluation audit?

Yes, an AI-SPEC.md file is required. The audit process checks execution logs against the defined evaluation strategy stated in the specification, meaning the audit cannot verify compliance without this foundational project-specific document.

When should I run an evaluation coverage audit?

Run an evaluation coverage audit after completing a complex feature implementation. This ensures all edge cases and performance benchmarks defined in the initial specification were properly tested and validated before moving to the next phase.

What are the limitations of automated evaluation audits?

Automated evaluation audits are limited to comparing execution logs against existing defined specifications. They cannot invent new evaluation criteria or test unlogged behaviors, meaning any gaps in the initial AI-SPEC.md will remain unaddressed by the audit.