Validate

Validation Skill

Validate AgentTask completion against success criteria and project standards.

When to Use

• Checking if work meets all requirements
• Validating file placement rules
• Ensuring quality standards before completion
• Reviewing subagent work output

Required Checks

• Success criteria satisfied
• File placement rules followed
• ALL-CAPS file names avoided (except allowlist)
• Summary/report files only in summaries/
• Memory updated when new knowledge created
• Tracking backend state is updated (GitHub/Linear/Jira/file-based)
• For GitHub parent-child items, native relationship is verified (body text alone is not accepted)

File Placement Validation

NEVER place:

• Summaries in docs/ or project root
• Memory entries outside memory/exports/
• Reports anywhere except summaries/

ALL-CAPS Allowlist

These files ARE allowed to be ALL-CAPS:

• README.md, LICENSE, LICENSE.md
• CLAUDE.md, SKILL.md, AGENTS.md
• CHANGELOG.md, CONTRIBUTING.md
• AUTHORS, NOTICE, PATENTS, VERSION
• MAKEFILE, DOCKERFILE, COPYING, COPYRIGHT

Summary Validation

Every summary/completion must include:

• What changed - concrete list of modifications
• Why it changed - rationale/requirements addressed
• How it was validated - tests or checks performed
• Risks or follow-ups - any remaining concerns

Validation Checklist

Before marking AgentTask complete:

- [ ] All success criteria met
- [ ] Changes match requested scope (no over-engineering)
- [ ] File placement rules followed
- [ ] Documentation updated as needed
- [ ] Git operations completed
- [ ] Summary is factual and complete

Validation Ownership

• Executing subagent: Performs initial validation
• Main agent: Reviews and confirms validation
• Hook system: Enforces file placement automatically