michi

道, "the way" my approach to building software, embodied in an agent-centric toolkit.

The Problem

221 tests passed. Two bugs escaped. The agent grades its own homework — and more tests won’t fix that.

The Iteration Cycle

Explore → Plan → Execute → Verify → Document. Each cycle builds richer context for the next. Spirals, not circles.

Verification

Five layers of verification. Co-designed scenarios. You can only give the agent as much rope as your verification can catch.

Nine Skills

Claude Code slash commands for every phase — bootstrap, explore, plan, execute, debrief, sustainability, scenarios, workshop, PR prep.

Core concepts

The principles and patterns that shape every Michi session.

Principles The Iteration Cycle Verification Paired & Entrusted modes Plan docs as contracts

Reference

The machinery — skills, scenarios, patterns, the docs structure itself.

Skills Scenario testing Patterns & anti-patterns Documentation structure Memory & cold starts

Start pairedYour first epic should always be Paired.The context that makes Entrusted viable doesn’t exist yet. Start slow, earn speed.

your-project/

# 1. Install the skills
cp -r michi/toolkit/skills .claude/skills

# 2. Bootstrap your project
/michi-bootstrap

# 3. Plan your first milestone
/michi-planning