Strategies
A strategy is a building goal with reasoning behind it — not a bag of skill names. Read What it is and Why it works even if you already know the practices; the reasoning tells you when to break the pattern.
Most sessions need one strategy. Running all seven at once is usually a sign you skipped Orientation — or skipped your lifecycle / project shape.
Prerequisite: Orientation. Vocabulary: Concepts. Lifecycle: How work flows. Architecture / shape: Architecture · Paths.
| Path | Draw these strategies first |
|---|---|
| Simple website | Orient → Craft and Harden → Ship (light) → Tidy |
| CLI | Orient → Track Work → Diagnose and Fix → Craft and Harden → Ship |
| Python package | Orient → Track Work → Craft and Harden → Ship |
| Monorepo | Full set; emphasize Track Work, Ship, Agent Hygiene, Diagnose and Fix |
| Compute | Ship + Craft; KISS before a second platform; secrets via ESC |
- Orient — Recover vision and situation; pick an achievable goal.
- Track Work — Make progress legible on issues, milestones, and PRs.
- Diagnose and Fix — Put out real fires with evidence-backed repair.
- Craft and Harden — Research, refactor, test, observe, document — without boiling the ocean.
- Ship — Readiness → merge → stage → production with sober gates.
- Agent Hygiene — Design, analyze, optimize agents; slap and drain when stupid.
- Tidy and Recover — Clear dangling workspaces, artifacts, caches; reclaim the room.