afc:validate

Validate consistency and quality across spec.md, plan.md, and tasks.md files.

7|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/jhlee0409/all-for-claudecode --skill afc-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: afc:validate
Source: https://github.com/jhlee0409/all-for-claudecode/tree/main/skills/validate
Command: npx skills add https://github.com/jhlee0409/all-for-claudecode --skill afc-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automatically validates the consistency and quality of critical development artifacts like specifications, plans, and tasks, preventing errors and ensuring alignment.

Core Features & Use Cases

  • Artifact Validation: Checks for duplication, ambiguity, coverage gaps, and inconsistencies across spec, plan, and task files.
  • Principles Compliance: Verifies adherence to defined architectural and coding principles.
  • Use Case: Before implementing a new feature, run this Skill to ensure the spec clearly defines requirements that are fully covered by the implementation plan and tasks, catching potential misunderstandings early.

Quick Start

Run the afc:validate skill to check the consistency of the spec and plan for the current feature.

Frequently Asked Questions about afc:validate

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

FAQPage Schema
How do I validate consistency between spec, plan, and task files?

To validate artifact consistency, run a check that scans spec.md, plan.md, and tasks.md files for duplication, ambiguity, coverage gaps, and misalignment before implementation begins.

What does artifact validation check for in software development features?

Artifact validation checks for duplication, ambiguity, coverage gaps, inconsistencies, principles compliance, and unidentified risks across your specification, plan, and task documents to ensure feature alignment.

When should I run spec and plan validation for a new feature?

You should run spec and plan validation before implementing a new feature, ensuring the specification clearly defines requirements that are fully covered by the implementation plan and catching potential misunderstandings early.

Can I limit the validation scope to specific artifacts or sections?

Yes, you can limit the validation scope by passing an optional argument to the validation process, restricting the consistency and quality checks to specific artifacts or sections within your feature documentation.

How do I check if my implementation plan covers all specification requirements?

To check if your implementation plan covers all specification requirements, perform an artifact validation that identifies coverage gaps and verifies alignment between your spec.md and plan.md files.