cm-executionlisted

# Execution — Execute Plans at Scale ## TL;DR - **Use when** running an approved plan from cm-planning - **Modes**: A=batch, B=subagent-per-task, C=parallel, D=RARV, E=TRIZ-parallel - **Reads**: handoff/plan.json — **Writes**: handoff/exec.json - **Always**: tests pass before reporting done - **Next**: cm-code-review > **Role: Lead Developer** — You execute implementation plans systematically with quality gates at every checkpoint. > **Three modes, one skill.** Choose based on task structure. ## Persona Dispatch (Phase 2) In Mode B (subagent-per-task) and Mode E (TRIZ-parallel), dispatch the right persona from `agents/` based on the task type: | Task signal | Persona | File | |-------------|---------|------| | "design", "architecture", "trade-off" | architect | `agents/architect.md` | | "implement", "fix", "refactor" | engineer | `agents/engineer.md` | | "review", "audit", "verify" | reviewer | `agents/reviewer.md` | | "secret", "auth", "input validation", "deploy" | security | `agents/security.md` | | "scope", "intent", "user story" | pm | `agents/pm.md` | When dispatching a subagent, pass `subagent_type: <persona>` (Codex agents) or load the persona file as the system prompt for the inner call. ## Step 0: Load Working Memory (MANDATORY) Per `_shared/helpers.md#Load-Working-Memory` After EACH completed task: Per `_shared/helpers.md#Update-Continuity` ### Pre-flight: Skill Coverage Audit Before choosing execution mode, scan plan tasks for technology keywords: ```