task-mgmt

Document project decisions by creating per-task briefing documents that enforce a standardized body with Objective, Reasoning, and Conclusion fields. This approach captures decision context and tracks task status through a simple lifecycle.

The best way to structure task documentation is using a YAML frontmatter with name and description, followed by a standardized body. This enforces consistent content structure across tasks to capture decision context and track status.

Create a new task file in the project-mgmt folder using a prescribed kebab-case naming convention like [task-name].tsk.md. Ensure the file contains required metadata sections and a complete Objective, Reasoning, and Conclusion structure.

Yes, track task status through a simple lifecycle from new to started, then to completed or cancelled. You can list open tasks stored as individual [task-name].tsk.md files in the project-mgmt directory for traceability.

Task management documentation requires a YAML frontmatter with name and description fields. This metadata ensures each task has a clear objective and is stored as a separate file for project traceability.

Per-task briefing documents standardize how tasks are created and tracked, ensuring each task has a clear objective, reasoning, and conclusion. Storing them as separate files in project-mgmt provides better traceability and decision context.