doc-tasks-validator

Name: doc-tasks-validator
Availability: InStock
Author: vladm3105

Validate TASKS documents against Layer 11 schema standards.

16|3|Updated Nov 10, 2025

Search Tags:#planning #validation #schema #tasks #traceability #docs

Ready to run

npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-tasks-validator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-tasks-validator
Source: https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-tasks-validator
Command: npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-tasks-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates Task Breakdown (TASKS) documents against Layer 11 schema standards to ensure completeness, correct structure, and traceability before IPLAN creation.

Core Features & Use Cases

Metadata Validation: Checks document_type, layer, artifact_type, tags, and custom_fields.
Structure Validation: Ensures required sections (1-12) and proper task/phase formatting.
Traceability Validation: Verifies cumulative traceability tags to Upstream/Downstream artifacts.

Quick Start

Validate a TASKS file such as TASKS-01-003_example.md against the Layer 11 schema to confirm structure and traceability.

Frequently Asked Questions about doc-tasks-validator

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

FAQPage Schema

How do I validate a TASKS document against Layer 11 schema?▼

TASKS document validation checks your Task Breakdown file against Layer 11 schema standards, verifying metadata, structure, required sections 1–12, traceability tags, and IPLAN readiness. Upload or reference your TASKS markdown file to generate a detailed validation report with errors, warnings, and compliance scoring.

What does TASKS schema validation check for?▼

Schema validation enforces document type, layer, artifact type, tag taxonomy, section presence, task formatting, implementation contracts, risk criteria, acceptance criteria, and cumulative traceability to upstream and downstream artifacts. It confirms your TASKS document is complete and IPLAN-ready.

When do I need to validate TASKS documents before IPLAN creation?▼

Validate TASKS documents before IPLAN creation to ensure structure completeness, correct traceability linkage, and compliance with Layer 11 standards. This prevents downstream rework and confirms your Task Breakdown is ready for planning automation.

Can I validate TASKS files with custom metadata and tags?▼

Yes, validation covers custom fields, tags, and metadata alongside required fields. The schema enforces tag taxonomy and validates both standard and custom metadata to ensure traceability and artifact integration across your workflow.

What output does the TASKS validation report provide?▼

The validation report generates detailed results including error lists, warning flags, section-by-section compliance checks, traceability verification outcomes, and an IPLAN-Ready score indicating overall document readiness for downstream planning.