martinizinglisted

# Martinizing Reads the **code as strategy** — interprets investment levels, architecture, and capability chains as a set of revealed strategic bets, surfacing choices, investment mismatches, and capability gaps through Roger Martin's lens. Unlike a technical-recommendations audit, it never checks code against per-skill rules. For the full finding category definitions, Phase 3 agent prompt template, and Phase 4 report format, see [references/scoring-rubric.md](references/scoring-rubric.md). ## Usage ``` /martinizing # Audit current working directory /martinizing ./src # Audit specific path /martinizing /path/to/repo # Audit any repo /martinizing --resume # Resume from last checkpoint in .claude/tmp/martinizing/state.md ``` One optional argument: the code path to audit. Defaults to current working directory. **This skill audits code only — it does not read or modify documentation files.** ## Prerequisites - **dev-planning** skill — structures the output into actionable implementation plans - Strategy framework reference bundled at [references/five-elements-of-strategy.md](references/five-elements-of-strategy.md) - **lode/strategy/** — strategic profiles are written here after Phase 4.5. Directory is created on first run. Files follow the naming pattern `{YYYY-MM-DD}-{repo-slug}.md`. These are permanent project memory — not deleted with `.claude/tmp/martinizing/`. ## Workflow ### Step R: Resume Check Before doing anythin