deepworkplan-execute

DeepWorkPlan — Execute

Execute a Deep Work Plan by working through its tasks sequentially, one at a time, validating and committing after each, and reporting progress — fluently inside the plan's authorization, without asking whether to continue after every successful task.

Shared resources (read at their moment, not upfront)

The compulsory set for this flow is the router SKILL plus this file: every rule the loop runs on — strict order, gate selection from the actual surface, STOP-on-fail, task-local closure, commit format, the state-update command, the Final Review — is stated inline in the steps below. A default session reads no guide, spec or shared companion before Task 1; companions load when their moment arrives. (This ordering is deliberate: reading companions "to be safe" is the failure mode this tiering removed.)

• Essential now (before the first task): ../shared/context.sh — run it (bash ../shared/context.sh) to resolve repo root, branch, agent tool and dwp_dir; its source is not part of this flow's reads. That is the whole t0 set — the operative rules the loop needs are inline below.
• Conditional — read only when the trigger fires:
  • v6.md (this directory) — read only when Step 2.0 detects a v6 or v7 plan; it carries the whole task loop.
  • delegation.md — read only when a v7 plan granting agent_delegation delegates a task.
  • ../guide/swarm.md §17 — read only when the agentkit addon is enabled (capacity check at each task boundary: ../shared/swarm.py capacity) or a handoff or succession is in play.
  • ../spec/LITE_PLANS.md — read only when the plan README declares Plan Format: Lite or a v2 state line (anchored task records, approval axis, promotion recovery).
  • ../spec/PLAN_STATE.md §4–§5 — read only when state.json and the README disagree (markdown wins — regenerate), when a takeover needs the checkpoint contract, or when update-state.py cannot run and a whole-file rewrite is unavoidable. The everyday needs are inline: bookkeeping order and the closed gate-record shape in Step 5 rules 5–6.
  • ../guide/execution.md — read §6.1 only when the Final Review task begins (the prose behind its five parts (a)–(e)); read the Multi-Project Commit Workflow only when the plan spans multiple repositories; read rule 6 only when a Dailybot report moment arrives with the addon installed. The loop rules (§6 rules 1–5) and completion tracking are already inline in Step 5 and Important Notes.
  • ../guide/authoring.md §5.3–§5.4 — read only when judging a task's test or security discipline.
  • ../guide/prompts.md §9 — read only when a resume scenario arises mid-execution (the resume sub-skill owns them).
  • ../shared/adaptation.md — read only when adapting a pack example or template command into repo-specific form; the operative rule — select from the actual surface, never a fixed command set — is inline in Step 5 rule 3.
  • ../shared/dwp-paths.md — read only when a plan folder cannot be located or the DWP_DIR override is in play (Steps 0–3 already inline .dwp/plans/<plan>/).
  • ../shared/troubleshooting.md — read only when something is already wrong (discovery failure, stale installation, missing test command, unsupported host capability, inconsistent plan state).
  • orchestrator.md (this directory) plus ../guide/orchestrator.md §13 — read only when Step 2.1 detects an orchestrator plan.
  • team-agents.md (this directory) plus ../guide/team-agents.md §14 — read only when Step 2.2 finds a Team Agents Configuration and team mode is selected.
  • ../create/addon-augmentations.md — read only when the Final Review runs its required local-review pass (load it even if the reviewer is not yet installed, so the missing-install finding path is available); the reviewer's own ../addons/ai-diff-reviewer/SKILL.md loads at that same moment, never before.
  • The repository's docs/TESTING_GUIDE.md — read only when a task's gate must be widened or derived.
  • ../guide/GUIDE.md — the routing index; consult only when a need is not covered by a section named above.
• Never by default: no other guide, spec, preset or addon file is read for this flow — not defensively, not "to be safe". Speculative reading is exactly what the tier above replaces: name the moment, then read.