Use after task-router classification when work touches a concrete engineering domain (frontend, backend/API, database, infrastructure/cloud, testing, security) — supplies that domain's delegation routing, verification contract, and danger list to embed in MKCREW delegation prompts.
Use before delegating coding or planning to MKCREW agents when git backup, worktree isolation, detailed prompts, allowed files, stop conditions, and verification are needed. Canonical source of truth for the planner read-only prompt, git-checkpoint commands, reply discipline, and delivery watchdog.
Use when asked to keep developing a project, run an autonomous senior developer loop, keep improving / iterate over milestones, or coordinate the MKCREW team across reviewable milestones. This skill owns milestone coordination only; for delegation prompts and git-backup mechanics it invokes safe-agent-delegation rather than duplicating them. Do not use for one-off single edits or initial task classification (use task-router).
Use at the start of broad, ambiguous, multi-step, risky, or MKCREW team tasks to classify the request, pick skills, pick agents/tier, set the git-safety level, and emit one routing block BEFORE any implementation. Use for a single classification pass at the start; for an ongoing autonomous build loop, route to senior-developer-loop and stop. It does not replace implementation skills; it selects them.
Use after a MKCREW task when experience should become durable: the same mistake recurs, reviewer flags a preventable issue, a worker misunderstands a delegation, a check is missing/flaky/too broad, the human corrects team behavior, or a workflow succeeds repeatedly and should be reusable. Converts experience into memory, skills, scripts, tests, or lessons. Not for implementing features or routing a fresh task.