task-lifecycle-manager

Task lifecycle management is automated by standardizing task folders under docs/Workstream_{Domain}/{Date}_{TaskName} with mandatory todo.md, spec.md, and report.md files. This enforces documentation-first state tracking to ensure code reflects documented progress across projects.

The "Documentation is State" rule ensures that your task checklists and structured files serve as the single source of truth for progress. It enforces automated synchronization checks to align your code with the documented checklist and generate final reports.

Create a new workstream task folder using the docs/Workstream_{Domain}/{Date}_{TaskName} naming convention and begin by writing todo.md as the driving plan. You must then populate spec.md and report.md to satisfy frontmatter-based discovery and strict validation.

Yes, task lifecycle automation explicitly satisfies frontmatter-based discovery and validates in-code references. It applies strict validation and state alignment across new task creation, progress synchronization, and artifact generation from Template to Finalize.

Automated synchronization checks align your code with the documented checklist using the task-syncer component. This validates state alignment and generates final reports, ensuring every task maintains a verifiable single source of truth.

Use standardized task folders when you need traceable docs and verifiable progress across engineering projects from Template to Finalize. This approach prevents misaligned code by enforcing documentation-first state tracking and generating structured artifacts like report.md.