task-execution-simple
Task Execution Simple
Use after task-preparation has finished task-local docs and routine follow-up, and the task is ready for straightforward execution.
Owns execution isolation, readiness, implementation edits, verification, implementation-caused docs/status updates, implementation review, and branch closing. It does not own roadmap decomposition or task-local spec.md/plan.md authoring.
Required Gates
| Gate | Required behavior |
|---|---|
| Branch | Default never implement on the current branch; create a dedicated task branch by default unless the user explicitly chooses otherwise or a worktree workflow is specifically needed. |
| Readiness | Handle execution isolation and any other pre-code readiness work before implementation edits. |
| Verification | Verify implementation and update docs/status in the same round when behavior, API shape, or task state changed. |
| Commit | Commit verified implementation work on the task branch before implementation review. If plan.md defines commit points, commit at those natural stable points after local verification for that slice. |
| Review | Stop for implementation review after the verified implementation is committed, before merge, destructive cleanup, or branch deletion. |
| Closing | Resolve only any remaining hard gate such as branch deletion or destructive cleanup after implementation review. |
After an implementation review pause, treat any clear forward-motion message as approval to follow the recommended non-destructive next step. Ask a separate approval question only for hard gates.
More from adol1111/doc-driven-spec-workflow
doc-driven-spec-workflow
Use when a docs-driven repository request is unclear about whether the next step is scaffold initialization, clarification, roadmap decomposition, or current-task execution.
36milestone-planning
Use when a request or repository needs roadmap decomposition before spec writing because milestone boundaries, module grouping, or independently reviewable tasks are unclear.
35task-spec-execution
Use when older prompts, installed workflows, or tests still refer to task-spec-execution and need a compatibility redirect into the split task-preparation or task-execution-simple stages.
35docs-workflow-bootstrap
Use when initializing, bootstrapping, creating, or scaffolding the minimum docs-driven workflow layout for a repository before roadmap planning, specs, or implementation tasks exist.
33task-preparation
Use when a docs-driven repository has a selected or selectable concrete docs/tasks task and needs task-local spec or plan governance before code execution.
10doc-driven:task-spec-execution
Use when a docs-driven repository has a selected or selectable concrete docs/tasks task and needs task-local spec or implementation governance before code changes.
1