plan

Draft a structured plan by providing a name and description to generate a plan body with YAML frontmatter metadata, which is then saved under CODEX_HOME/plans. This converts vague coding objectives into an executable roadmap documenting scope, requirements, and action items.

YAML frontmatter is required metadata at the top of a plan file that enforces a contract specifying a name and description. You need it to validate plan names and manage structured task workflows for complex coding projects.

Manage existing coding plans using built-in read, update, delete, and list workflows that operate on the CODEX_HOME/plans directory. Reference and modify plan bodies through helper scripts to keep task documentation current.

Yes, use this plan tool for architecture reviews, project planning, and complex coding tasks. It documents scope, requirements, action items, testing validation, and risks by enforcing structured frontmatter metadata for each plan.

Frontmatter-enforced plan validation requires a strict contract with a name and description, meaning plans missing these fields will fail validation. Plan names are validated to ensure they meet the required format before saving to the plans directory.

No, the plan workflow operates independently without external dependencies, relying solely on helper scripts to generate, save, and reference plan bodies. It functions within the CODEX_HOME/plans directory using standard YAML frontmatter.