worktracker-decompositionlisted

# WORKTRACKER Decomposition Skill > Transform monolithic WORKTRACKER files into multi-file hub-and-spoke architectures for surviving context rot. --- ## Purpose The WORKTRACKER Decomposition skill provides automated analysis and transformation of large, monolithic work tracking files into a **Hub and Spoke architecture**. This pattern addresses **Context Rot** - the phenomenon where LLM performance degrades as context windows fill. ### The Problem As work tracking files grow beyond ~500 lines: - **Context consumption** increases (less room for actual work) - **Navigation** becomes difficult (finding active work requires scrolling) - **Compaction vulnerability** increases (key state lost after context compaction) - **Parallel work blocked** (single file means sequential updates only) ### The Solution The Hub and Spoke pattern: - **Hub** (`WORKTRACKER.md`): <150 line navigation index with status dashboard - **Spokes** (`work/*.md`): Detailed phase files, each self-contained - **Progressive Detail**: Active work gets maximum detail, completed work stays minimal --- ## Commands ### Analyze WORKTRACKER Analyze a WORKTRACKER file to assess whether decomposition is needed. ``` @worktracker-decompose analyze <path> ``` **Arguments:** - `path`: Path to WORKTRACKER.md file (required) **Example:** ``` @worktracker-decompose analyze projects/PROJ-002/WORKTRACKER.md ``` **Output:** ``` WORKTRACKER Analysis Report =========================== File: projects/PROJ-002/WORKTRA