doc-driven:task-spec-execution
Task Spec Execution
Use this skill after roadmap structure exists and one concrete task is selected or ready to be selected.
Composition
- Entry: reached from
doc-driven-spec-workflowordoc-driven:milestone-planningafter a concrete task exists or is selected. - Owns: task-local
spec.md, optional task-localplan.md, readiness checks, implementation governance, verification, docs/status updates, and branch closing. - Does not own: minimum docs scaffold bootstrap, milestone boundary decisions, module grouping, roadmap-layer task creation, or planning-stage templates.
- Handoff: return to
doc-driven-spec-workflowafter one concrete task checkpoint and branch closing are resolved.
Core Rules
Spec and Plan
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-execution-simple
Use when task-local spec or plan work is complete and a concrete docs/tasks task should be implemented through the repository's simple direct execution path.
11task-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.
10