魔法

mahou

Discipline, automated.

View on GitHubRead docs

The name

mahou (魔法) is Japanese for magic. Here, magic is the discipline of doing the right work in the right order — root cause before fix, design before code, verify before ship.

Discipline is magic

Root cause before fix

Investigate before acting. One hypothesis, one test, verify before continuing.

Design before code

Spec and plan before implementation. Know what you're building before you build it.

Verify before ship

Check the build against the spec. Nothing ships without passing verification.

How it works

  1. Project

    Initialize projects, research approaches, and map existing codebases.

  2. Feature

    Brainstorm specs, orchestrate implementation, and review against the plan.

  3. Lifecycle

    Resume sessions, verify the build, and ship pull requests.

The workflow

/mahou-brainstorm

Design to spec before code.

/mahou-orchestrator

Execute the plan task-by-task.

/mahou-verify

Check implementation against spec.

/mahou-ship

Push, create PR, ship it.

Commands

/mahou-brainstorm

Design to spec before writing code.

/mahou-orchestrator

Execute a plan task-by-task via subagents.

/mahou-verify

Check implementation against the spec.

/mahou-ship

Push, create a PR, and filter planning artifacts.

/mahou-debug

Root-cause investigation before any fix.

Quick start

GitHubDocsShare freely.