oat-project-plan-writing

To enforce a standardized plan.md format, validate frontmatter keys like oat_plan_source, oat_status, and oat_ready_for, and ensure required sections such as Reviews and Implementation Complete are present. This prevents inconsistencies in project planning workflows.

Required frontmatter keys in an OAT project plan file include oat_plan_source, oat_status, and oat_ready_for. Validating these keys ensures the plan maintains stable task IDs and adheres to canonical format invariants for execution readiness.

To prevent accidental deletion of review rows when updating a plan.md, apply review table preservation rules during plan mutation. This maintains historical data by blocking the removal of existing review rows while allowing new entries.

A valid project plan markdown file must contain required sections including Reviews and Implementation Complete. Checking for these sections guarantees the plan is correctly formatted and ready for execution before any tasks begin.

To manage stable task IDs in project management documentation, enforce canonical format invariants during plan authoring. This keeps task identifiers consistent across mutations, preventing reference errors during execution and resume operations.

No dependencies are required to validate plan files in the current directory. You can directly check the plan.md file against the canonical format invariants, verifying frontmatter, required sections, and review table rules without external tools.