plan-validation

To validate planning documents, this skill checks 1-definition.md, 2-plan.md, and 3-spec.md for completeness, consistency, and unresolved open questions. It outputs actionable validation results with status and detailed issues for remediation.

Checking ticket planning docs for ambiguity involves validating core files like 3-spec.md and 2-plan.md to detect unresolved open questions and missing prerequisites. The process provides structured feedback with detailed issues to guide remediation.

Yes, you can use this validation process for project-management workflows. It applies to ticket planning by validating definition, plan, and spec documents, plus environment setup and tests, to ensure roadmap alignment and implementation readiness.

Planning document validation detects outdated decisions and unresolved open questions by analyzing 1-definition.md, 2-plan.md, and 3-spec.md for consistency. It outputs a ready-for-implementation report with structured status checks and actionable issues.

Limitations of planning docs validation include its strict dependency on specific file formats like 1-definition.md, 2-plan.md, and 3-spec.md. It requires these core planning documents to exist and be properly structured to produce actionable validation results.