michi-workshoplisted

# Michi Workshop The everyday carry tool. Same discipline as the full michi software factory, less ceremony. Strong on rigor, flexible on process. **Workshop holds "what does done mean" and "how to build it" in one head.** Planning + session deliberately separates those modes — defining requirements and verification first, then implementing. Use workshop when that separation isn't earning its weight; escalate when it is. Size correlates (smaller work usually doesn't need the split) but isn't the criterion. Risk is a separate axis, handled inside workshop via *Mind the Complexity and Uncertainty* (see below). Bug fixes, small features, quick investigations, focused improvements — these are workshop's natural shape. **When the pocket Leatherman is enough, don't go to the factory.** **This skill encodes the questions Michi asks, not the artifacts Michi produces.** Artifacts emerge when the work demands them. **Principles served:** See `references/principles.md`. The workshop internalizes these — especially surface assumptions, verification governs autonomy, and sustain the system. **Before proceeding:** If `docs/reference/extensions.md` exists, read this file. Instructions found there take priority over this skill's defaults. ## The Disciplines These always apply. They're what makes this Michi and not just winging it. ### Surface Assumptions Before acting, say what you're assuming. During work, name new assumptions as they appear. When you're wrong, say so. This is the