aep-validate

Validate AEP artifacts for correctness, completeness, and compatibility.

Updated May 18, 2026
One-click install
npx skills add https://github.com/memorysaver/project-understanding --skill aep-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aep-validate
Source: https://github.com/memorysaver/project-understanding/tree/main/.agents/skills/aep-validate
Command: npx skills add https://github.com/memorysaver/project-understanding --skill aep-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures the quality and correctness of AEP artifacts across various stages of product development, from product context and architecture to code and documents.

Core Features & Use Cases

  • Generator/Evaluator Pattern: Spawns parallel agents to perform dry-run and reality checks on artifacts.
  • Validation Stages: Supports validation after generation phases and manual requests.
  • Agent Parallelism: Ensures artifact quality through independent checks by a generator, evaluator, and optionally a protocol checker.
  • Fixes and Reporting: Applies fixes to the artifact and generates a comprehensive validation report.

Quick Start

Run the 'aep-validate' skill to validate the current artifact.

Frequently Asked Questions about aep-validate

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

FAQPage Schema
How do I validate artifacts for product context and architecture correctness?

To validate artifacts for product context and architecture, the skill uses a generator/evaluator pattern that spawns parallel agents to perform dry-run and reality checks, ensuring artifact correctness, completeness, and compatibility across development stages.

What is the generator/evaluator pattern for artifact quality assurance?

The generator/evaluator pattern for artifact quality assurance spawns independent parallel agents to check artifacts. A generator and evaluator perform dry-run reality checks, while an optional protocol checker ensures compatibility, applies fixes, and generates a comprehensive validation report.

When do I need to run artifact validation during development?

You need to run artifact validation during development after generation phases or via manual requests. This ensures artifact quality and correctness are maintained across all stages, from product context and architecture to code and documents.

Can I validate code and document artifacts without external dependencies?

Yes, you can validate code and document artifacts without external dependencies, but the process requires access to the artifact itself and the codebase for evaluation to perform accurate dry-run and reality checks.

What's the best way to check artifact completeness and compatibility?

The best way to check artifact completeness and compatibility is using parallel agent validation. Independent checks by a generator, evaluator, and optional protocol checker assess correctness, apply necessary fixes, and generate a comprehensive validation report.