michi-docslisted

# Michi Docs Michi's working docs are written for an agent: dense, additive, decision-log shaped, exhaustive because omission costs the agent context. That is the right shape while the human is in the loop. It fails at **handoff** — when the work has to be understood by someone who wasn't in the sessions. This skill derives the reader-facing layer. **The agent-facing sources stay as they are.** Epics, plans, debriefs and journals are the record; they are not the deliverable, and this skill does not rewrite them. **The gap this fills:** an engineer joining the project, a teammate receiving a module, a reviewer picking up a branch. They need to know what the thing is, what it must do, what constrains it, and where to start reading — in that order. The epics answer none of those questions first. **Principles served:** Progressive Detail — size the document to its audience and moment. Essential, Incidental, and Noise — the operator's trust calibration is essential to the operator and noise to a newcomer. Clarify before Asserting — every claim about the system gets checked against the system. See `references/principles.md` and `references/docs-structure.md`. **Before proceeding:** If `docs/reference/extensions.md` exists, read this file. Instructions found there take priority over this skill's defaults. ## Targets **The target decides the output shape.** Ask for it if the invocation doesn't say. ``` /michi-docs project → the living project docs /michi-docs sco