refinelisted

## Runtime persistence `.principled/` (in cwd) is the natural runtime emplacement for principled-related artifacts. At intake, read whatever is there if any — prior context may inform this work. When this skill produces durable artifacts, write them to `.principled/` too. Skip if absent. ## Routing Guidance - IMMEDIATELY before merging or committing significant code changes (SIMPLIFY or REVIEW). - IMMEDIATELY when encountering functions over 40 lines, nesting beyond 3 levels, or duplicated code blocks (SIMPLIFY). - IMMEDIATELY after completing significant work needing independent quality verification (CRITIQUE). - IMMEDIATELY when producing documentation, READMEs, or human-readable text (POLISH). - When consolidating reflection or critique findings into durable project memory (MEMORIZE). - Do NOT use for architectural decisions or greenfield development — use `plan-lifecycle PLAN mode` instead. - CONTRAST with update-docs: that updates existing docs; this improves prose quality (POLISH). - CONTRAST with ddd: refine improves quality of existing artifacts (present, corrective); ddd performs structural analysis (architecture, quality, transparency, API). Use refine when the issue is known and needs fixing; use ddd when a specific structural question surfaces. - CONTRAST with kaizen: refine is on-demand quality improvement; kaizen provides continuous guardrails. Use refine after completing work; use kaizen during every code decision. - CONTRAST with sadd JUDGE: refine provides