dorodango

# Dorodango Polishing Workflow Named after the Japanese art of polishing a ball of dirt into a high-gloss sphere. Applied to code: take the initial implementation (the "mud ball") and refine it through successive quality passes until it shines. ## When To Use - After initial implementation is complete and tests pass - Code works but needs refinement across multiple quality dimensions - Preparing code for review or release - Resuming a previous polishing session ## When NOT To Use - Code does not compile or pass basic tests (fix first) - Single-dimension improvement needed (use the specific skill directly: pensive:code-refinement, etc.) - Greenfield design phase (use brainstorming instead) ## Pass Sequence Four quality dimensions, each a self-contained pass: 1. **Correctness** - run tests, fix failures 2. **Clarity** - code readability and structure 3. **Consistency** - naming, patterns, style alignment 4. **Polish** - documentation, error messages, edges See `modules/pass-definitions.md` for detailed scope of each pass type. ## Convergence Model - Each pass targets one dimension - A pass that finds `issues_found: 0` marks that dimension as **converged** - Convergence is irreversible per run; a converged dimension is not re-run - When all 4 dimensions converge, polishing is complete - Maximum 10 total passes (hard limit) - If not converged after 10 passes, surface state to human with recommendation to split into smaller units ## State Persistence State...