| name | execute-task |
| description | Execute the next available implementation task from a project task list. Use when Codex is asked to pick up a pending task, work from tasks/prd-[feature-name]/tasks.md, implement a PRD or tech-spec task, continue a task backlog, or complete and mark project tasks done end to end. |
Execute Task
Core Workflow
Use this skill to identify the next available task, gather the required project context, implement the work, verify it, and update the task list.
Read references/execute-task.md before starting. Treat it as the canonical task-execution prompt for this skill.
Execution Rules
- Load the task definition, PRD, tech spec, project rules, and relevant project skills before editing.
- Identify and load additional skills based on the technologies involved in the task.
- Use Context7 MCP documentation for the languages, frameworks, and libraries used by the implementation.
- Summarize the selected task before implementation using the format in
references/execute-task.md.
- Create a concrete approach plan, then start implementation immediately.
- Follow project standards without workarounds.
- Run focused validation for the changed behavior.
- Mark the completed task in
tasks.md after the implementation and validation are complete.
Expected Inputs
Default file locations:
- PRD:
./tasks/prd-[feature-name]/prd.md
- Tech spec:
./tasks/prd-[feature-name]/techspec.md
- Tasks:
./tasks/prd-[feature-name]/tasks.md
- Project rules:
.codex/rules/
- Project skills:
.codex/skills/
If multiple task directories exist, inspect the task lists and choose the next actionable unchecked task unless the user specified a feature or task.