Issue Tree Decomposition Use when a broad initiative or recurring review needs to be turned into a structured set of future GitHub issues. When to use - User asks to "create future gh issues" - There is one umbrella issue but implementation needs multiple focused tracks - You want to split work by lanes such as operations, knowledge, automation, reporting - You want Claude subagents to help with analysis, but repo writes must stay in the main session Core pattern 1. Identify the umbrella issue and current related issues. 2. Add or update a single documentation page that describes the initiati…