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.