moh-implementation-flowlisted

# Moh Implementation Flow Use this companion for **non-trivial implementation work**: work that needs exploration, more than one coherent change, or could be interrupted by a turn budget or concurrent work. It supplements the implementation workflow; it does not replace the issue or its acceptance criteria. ## Start safely 1. Read the issue or specification and the repository instructions. 2. Create a dedicated branch **before exploration**. Do not mix the work with another task or commit unrelated working-tree changes. 3. When investigation has independent, read-only questions, delegate them to subagents in parallel. Keep dependent investigation in sequence; do not create parallelism merely for its own sake. 4. Confirm a product decision or a TDD seam only when it is genuinely unresolved. Once required decisions are settled, continue autonomously. ## Build in verified vertical slices Implement one coherent, observable behavior at a time: 1. Establish the agreed test seam and add the smallest useful test where applicable. 2. Make that behavior work. 3. Run the relevant targeted checks and typechecking. 4. Continue with the next slice only after the current behavior is verified. For non-trivial work, make an **atomic intermediate commit** after a verified, coherent, recoverable slice. A commit must contain only the work for that slice and must exclude unrelated working-tree changes. Do not fragment trivial changes into artificial commits: make an intermediate commit onl