validate

Validate codebase quality against Draft context documents and workflow.md settings.

39|6|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/mayurpise/draft --skill validate-mayurpise
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/mayurpise/draft/tree/main/skills/validate
Command: npx skills add https://github.com/mayurpise/draft --skill validate-mayurpise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft-driven validation ensures codebase quality by inspecting architecture, product context, and tech constraints to prevent architectural drift and security gaps.

Core Features & Use Cases

  • Project-wide validation: Assess the entire repository against draft/architecture.md, draft/tech-stack.md, and draft/product.md.
  • Track-level validation: Validate specific tracks based on changed files and acceptance criteria.
  • Config-driven execution: Respect workflow.md settings for auto-validation and block-on-fail behavior.
  • Reporting: Generate a comprehensive validation report at draft/validation-report.md.

Quick Start

Use the /draft:validate command to run a full validation across the project, or /draft:validate --track <track-id> to validate a single track. After execution, review draft/validation-report.md for findings.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I automate codebase quality checks for architectural conformance and security?▼

You can automate codebase quality checks by validating Draft context documents like architecture.md, tech-stack.md, and product.md to enforce architectural conformance, security, and spec-compliance across your repository.

What is draft-driven validation and how does it prevent architectural drift?▼

Draft-driven validation inspects architecture, product context, and tech constraints documents to prevent architectural drift and security gaps by ensuring the codebase conforms to defined specifications.

How do I validate a specific track based on changed files and acceptance criteria?▼

You can validate a specific track by running a track-level validation command with a track ID, which checks only the changed files and acceptance criteria for that track instead of the entire project.

Can I configure validation to block workflows automatically when checks fail?▼

Yes, you can configure auto-validation and block-on-fail behavior by adjusting workflow.md settings, which control execution requirements and whether the workflow stops upon validation failure.

Where does the codebase validation report get generated after execution?▼

The codebase validation report is generated at draft/validation-report.md, providing a comprehensive summary of all findings after the validation execution completes across the project or track.

Do I need Draft context files to run spec-compliance validation on my project?▼

Yes, spec-compliance validation requires Draft context files to determine validation rules, scope, and execution requirements, reading documents like architecture.md and product.md to assess the codebase.