improve-solutionlisted

# Improve Solution — Conversation-to-Documentation Propagation ## Trigger `/improve-solution [dir]` after a conversation that produced decisions, corrections, or overrides about a solution design. `dir` is the directory holding `design-doc.md` and `implementation-plan/implementation_plan_outline.md` (if omitted, discover it from the conversation — e.g. `.designs/<issue>/` — and confirm the paths before editing). ## The Contract This Skill Enforces The consumer of these documents is ALWAYS an agent, an LLM, or a formula/SKILL executing what is written. It is NEVER a human. An agent consumer takes whatever text it lands on literally — it does not arbitrate between a correction section and the stale text below it. Therefore: **RULE 1 — Single truth, stated everywhere.** After this skill runs, ANY section of either document read in isolation states the current decision. A document that needs a precedence rule to be read correctly is BROKEN for agent consumption. **RULE 2 — Sources are edited; derived documents are reconciled whole.** `design-doc.md` is the source of truth. `implementation_plan_outline.md` is derived from it. A derived document is never patched with correction blocks — it is regenerated by the project's planning pipeline when available, or fully rewritten section-by-section to match the source. **RULE 3 — Batch propagation, never incremental.** Collect ALL decisions first, then apply them in ONE propagation pass against a complete impact map. Editing per-de