Task Decomposition When to Use Activate this skill when: - A feature or objective requires 4 or more implementation steps - Changes span multiple files across backend and frontend layers - The user says "break this down", "decompose", "create subtasks", or "what are the steps" - Tracking progress across context windows or sessions is needed - A output (module map, risks, acceptance criteria) needs to be broken into atomic, executable tasks - Work needs to be parallelized across multiple agents or developers Expected input: Read (or ) produced by . This file contains the module map, risks, and…