thinkinglisted

# Thinking Move from ambiguity to a decision that is specific enough to act on and test. Use this as an orthogonal workflow skill alongside any relevant domain or repository skills. It does not replace security review, test strategy, prompt work, story preparation, documentation, or implementation guidance. Family boundary: **thinking** forms a candidate; **recursive-thinking** stress-tests an existing candidate; **dream-thinking** is an explicitly requested creative retrospective after experience. None requires the others to run first. ## Core cadence Run the skill through one simple loop: - understand what is stuck - explore only enough to improve the decision - identify what matters - choose what changes next ## Route by bottleneck - **Problem framing:** the goal, affected stakeholder, constraint, or success signal is unclear. - **Option discovery:** the problem is clear but the plausible approaches are not. - **Assumption testing:** no candidate has won yet, and the choice depends on uncertain beliefs or missing evidence. - **Systems analysis:** incentives, feedback loops, dependencies, or second-order effects could make a local improvement harmful overall. - **Decision convergence:** enough context exists to compare serious options and recommend a next move. Use **recursive-thinking** instead when the main job is to challenge, premortem, or find weaknesses in an already-formed plan, diagnosis, design, or recommendation. Switch to the appropriate execution or art