cc-pseudocode-programming

Design a routine in pseudocode before writing it. Iterating on intent is cheaper than iterating on code, and four questions catch the expensive mistakes early:

Question	Why
Can you name it clearly?	Naming difficulty signals an unclear design — clarify purpose first
Is there pseudocode before the code?	Refining pseudocode is cheaper than refining code
Do you understand why it works?	Working code you can't explain probably doesn't really work
Did you consider an alternative?	The first design is rarely the best

If the user asks to skip pseudocode, comply or surface the tradeoff once (the routine will likely cost more in debugging) — don't refuse.

Shared CC vocabulary and thresholds (cohesion, parameters, routine length): Read(${CLAUDE_PLUGIN_ROOT}/references/cc-foundations.md).

When the routine is exempt

Skip the process only when one of these holds: