Map Framework

After mapify upgrade, Claude can invoke any MAP skill through the Skill tool on your behalf except /map-release, which remains manual-only. Workflow confirmation gates still apply; /map-upgrade requires explicit consent for a major version.

Why MAP Exists

Most AI agents rush straight to code — fast wrong answers, silent rework.

Common failure modes MAP eliminates:

- AI silently makes architecture decisions you did not approve.
- One prompt produces a large diff that is hard to review.
- Tests are written around the generated implementation, including its mistakes.
- The output compiles, but you cannot explain why the design is correct.
- The next session forgets the gotchas you already paid to discover.

MAP moves engineering judgment earlier: write down the behavior, split the work into small contracts, verify each stage, review against the spec, and save lessons for the next run.

Skill maintainers can use mapify skill-eval optimize  --provider claude|codex --apply
to update only the selected provider's description in the shared template source;
the opposite provider stays unchanged (details).

Quick Start

1. Install

Requires Python 3.11+, and python3 on your PATH must be that interpreter — the
installed hooks and .map/scripts/ runners execute through a #!/usr/bin/env
python3 shebang, not through the interpreter that ran mapify. mapify init
checks it up front and tells you what to fix (details).
For Go projects requiring build tags, set checks.go.tags: integration,netgo in
.map/config.yaml for the Stop hook's build check (configuration).

2. Initialize your project

Claude Code is the default provider. Cross-AI review compares explicit host and
reviewer adapter vendors; same-vendor or unknown provenance is not labeled
independent (details).
An offline…