validate

Validate ADLC phase artifacts for frontmatter and structural readiness.

159|41|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/atelier-fashion/adlc-toolkit --skill validate-atelier-fashion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/atelier-fashion/adlc-toolkit/tree/main/validate
Command: npx skills add https://github.com/atelier-fashion/adlc-toolkit --skill validate-atelier-fashion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates ADLC phase artifacts to ensure only quality, approved outputs move forward, reducing rework and misalignment.

Core Features & Use Cases

  • Frontmatter and artifact validation across spec, architecture, tasks, and implementation phases to ensure completeness and consistency.
  • Phase-detection logic that derives the current phase from existing artifacts and applies the correct validation checks.
  • Produces a structured validation report with clear blockers, warnings, and recommended next steps to enable safe progression.

Quick Start

Validate the current repository's ADLC artifacts to determine readiness for the next phase.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I validate ADLC phase artifacts before advancing to the next stage?

To validate ADLC phase artifacts, the system identifies and checks your spec, architecture, tasks, and implementation files. It verifies frontmatter validity, phase-appropriate structure, and alignment with acceptance criteria to ensure readiness for safe progression.

What is the best way to check if my architecture and spec artifacts are aligned?

Checking architecture and spec alignment requires validating the relationships between ADLC artifacts. The system applies phase-detection logic to derive the current phase and verifies that structural conventions and frontmatter match across your defined artifacts.

How does phase detection work when validating software development artifacts?

Phase detection works by deriving the current phase from existing repository artifacts. It then applies the correct validation checks specific to the spec, architecture, tasks, or implementation phase to ensure consistency and completeness.

Can I get a validation report with blockers and warnings for my project artifacts?

Yes, validating your project artifacts produces a structured validation report. This report provides clear blockers, warnings, and recommended next steps to help you resolve issues and enable safe progression to the next phase.

Do I need any dependencies to validate ADLC artifacts in my repository?

No dependencies are required to validate ADLC artifacts in your repository. The validation process operates directly on your existing phase artifacts, checking frontmatter and structural conventions without external tool dependencies.

Why does my ADLC artifact validation fail when moving from spec to architecture phase?

ADLC artifact validation fails when phase-appropriate structure or frontmatter is missing or misaligned. The validation checks enforce defined conventions and acceptance criteria, producing specific blockers in the report to prevent misaligned outputs from advancing.