execute-tasklisted

# /execute-task The execution layer of the planwright pipeline (REQ-E1.1–REQ-E1.5): take one ready unit (a single task or a cohesion bundle) from a Ready or Active spec with a signed-off kickoff brief and carry it from a failing test to a draft PR. `/orchestrate` dispatches it into a prepared worktree; a human may also run it inside one. It works from the kickoff brief, the durable contract (D-3), not by re-reading the spec, and **never** creates worktrees (D-37, D-44), **never** merges, and **never** marks a PR ready — sign-off and merge are the human's two reserved controls. ## Doctrine This skill is procedure, not doctrine. Read the manifest's rule docs via `scripts/resolve-rule-doc.sh <doc-name>` (under the resolved planwright root); their definitions govern the concepts this skill names. Per `doctrine/instruction-hygiene.md`, `run-start` entries load before work begins, `point-of-use` entries at the named step or branch. **Invoking plugin scripts (REQ-D1.1, D-7).** Call `scripts/<name>.sh` by the **resolved literal absolute path**, never `$VAR/scripts/<name>.sh` — `doctrine/plugin-script-invocation.md`. If a manifest doc does not resolve — at run start or its point of use — halt naming the missing doc and the chain consulted (REQ-K1.7). `decision-domains` degrades gracefully instead: absent, note it in one line, skip the drift check, and use engineering judgment. Doctrine: run-start spec-format (status lifecycle, anchors, freshness gate) Doctrine: run-start proport