worktracker-decomposition

Decomposing a monolithic project tracker file prevents context rot by splitting it into a hub-and-spoke structure. A compact hub file holds the navigation graph, while per-phase spokes keep relevant context within reach for better readability.

The best way to organize multi-phase work trackers is a hub-and-spoke architecture. This structure uses a central hub file for navigation and status dashboards, alongside separate per-phase files to maintain coherence and preserve state across sessions.

You need to decompose a monolithic work tracker when its size degrades readability and navigation. Large, multi-phase project files benefit from decomposition into per-phase spokes to keep context manageable and prevent context rot.

Yes, you can preserve session context across multiple phases after splitting a project tracker. The hub-and-spoke structure implements session context tracking, quick status dashboards, and navigation links to maintain state and enable resume capability.

Yes, the hub-and-spoke tracker structure supports templates for new project phases. It provides standardized phase and category templates, along with supported commands for analysis, execution, and validation to maintain coherence across files.

To start splitting a single work tracker file, you decompose it into a central WORKTRACKER.md hub file and per-phase spoke files. This creates a navigation graph and quick status dashboard to preserve project state across sessions.