discovery-treeslisted

## Context marker 🌳 When the skill activates, begin the first commentary update with `🌳` and a concise `Using discovery-trees ...` announcement. Do not repeat the marker on later updates unless another skill activates. # Discovery Trees Use a Discovery Tree as a plan-backed information radiator for the work being discussed. Keep it in the conversation’s plan state, never as a repository artifact. Its purpose is to expose the smallest useful picture of progress and make the next decision easy. For the practice’s origin and broader mindset, consult [references/industrial-logic-discovery-trees.md](references/industrial-logic-discovery-trees.md) when the user asks about the rationale, history, or adaptations of Discovery Trees. The rendering and communication workflow in this skill remains the source of truth for agent behavior. ## When to render Render a fresh tree in the conversation when you: - propose a new plan or turn a specification into planned work; - revise a plan because scope, ordering, dependencies, or understanding changed; - complete a planned task; or - uncover work that changes the next decision. Do not wait for a formal planning ceremony. Discovery Trees support just-in-time planning, so add a small branch when new work is learned rather than pretending it was known from the start. ## Maintain the tree in the plan Treat the plan as the durable source of truth for the current Discovery Tree. Before rendering a new tree, read the existing plan record.