task-management

You can track implementation plans and task state by maintaining a temporary workspace for orchestration metadata and persisting final plans, reports, and issues to configurable documentation paths. This separates transient state from permanent records to ensure progress is never lost.

Completion reports are generated through the Documenter workflow, which executes tasks with progress tracking and writes the final report to configured documentation paths. This provides an auditable record of the completed implementation work.

Yes, you can resume failed orchestrations and recover interrupted task management processes. The system logs non-blocking documented issues and allows you to pick up the orchestration state from where the failure occurred.

Task management handles workspace cleanup through auto-cleaning of completed workspaces after a configurable retention period. This prevents clutter from temporary orchestration metadata while preserving permanent documentation.

The best way is to use a two-tier workspace and documentation approach, storing orchestration metadata and task state in a temporary workspace while persisting final plans, reports, and issues to separate, configurable documentation paths for clear task ownership.

Yes, the task management process satisfies requirements for JSON-based progress and tasks files. It tracks individual tasks, such as feature identifiers, within workspace JSON files during the orchestration execution.