plan-dev-validate

You can validate development plans for SDD compliance by running the validator command against your document path, optionally using the --all flag to check multiple files.

The 5-field TASK-N structure in SDD development plans requires tasks to include subtasks, dependencies with correct ordering, and cycles. Validation enforces this structure to ensure proper task decomposition and dependency tracking.

Plan validation is needed after creating or modifying a development plan, during code review, or before a commit. Running validation at these stages ensures SDD compliance before changes are merged.

Yes, the SDD plan validator checks INFRA limits, responsibility markers, and TC traceability. It enforces all mandatory metadata and structural fields required by SDD standards.

Automated SDD plan validation enforces structural compliance including frontmatter, TASK-N fields, dependencies, and INFRA limits, but cannot assess the qualitative technical correctness of the planned implementation itself.