Thermo-Nuclear Plan

Use this skill when writing or revising an implementation plan — before coding. Push for code judo: reframings that achieve the same goal with fewer phases, workstreams, concepts, and special-case branches. Do not stop at making each step concise. Ask whether whole categories of work can disappear because the approach can be simplified.

Core Prompt

Produce a rigorous implementation plan for the requested idea or change. Rethink how to structure the work so the implementation stays simple, modular, and maintainable without changing the goal. Prefer fewer phases, clearer ownership boundaries, and plans that avoid incidental complexity instead of scheduling around it. Be ambitious: if a clearer path involves reframing scope, sequencing, or decomposition, propose it. Be thorough. Measure twice, cut once.

Non-Negotiable Additional Standards

Apply the Core Prompt above, plus these explicit planning rules:

0. Be ambitious about structural simplification.
   • Do not stop at "we could combine these steps."
   • Look for reframings where whole phases, workstreams, migration paths, or feature flags disappear.
   • Prefer the plan that will feel inevitable in hindsight once someone implements it.
   • Assume there is often a code judo move: a sequencing or decomposition choice that uses the existing architecture and makes the work dramatically smaller and clearer.
   • If you see a path to avoid complexity rather than document and schedule around it, push hard for that path.