create-tasks

name	create-tasks
description	Create implementation task lists and individual task files from an existing PRD and Tech Spec. Use when Codex is asked to write, generate, create, draft, or update feature tasks, implementation tasks, task breakdowns, delivery plans, or task files based on tasks/prd-[feature-name]/prd.md and tasks/prd-[feature-name]/techspec.md.

Create Tasks

Use this skill to create developer-ready task files from a PRD and Tech Spec without implementing code.

Required Workflow

1. Confirm inputs.

   • Identify the feature slug.
   • Confirm the PRD exists at tasks/prd-[feature-name]/prd.md.
   • Confirm the Tech Spec exists at tasks/prd-[feature-name]/techspec.md.

2. Analyze the PRD and Tech Spec.

   • Read both documents completely.
   • Extract requirements, technical decisions, main components, dependencies, risks, and test needs.
   • Read relevant project rules under .codex/rules/ and relevant skills under .codex/skills/.

3. Propose high-level tasks for approval.

   • Before generating any file, show the list of high-level tasks to the user for approval.
   • Keep the list to 10 or fewer main tasks.
   • Make each task a well-defined deliverable.
   • Order tasks logically, with dependencies before dependents.
   • Ensure each task has a clear test set that supports its functionality and business goal.

4. Generate files only after approval.

   • Create tasks/prd-[feature-name]/tasks.md using references/tasks-summary-template.md.
   • Create one individual task file per main task using references/individual-task-template.md.
   • Name individual files tasks/prd-[feature-name]/[num]_task.md, where [num] matches the main task number.

5. Write task content.

   • Use X.0 format for main tasks and X.Y format for subtasks.
   • Include subtasks, mandatory requirements, success criteria, tests, and relevant files.
   • Include unit and integration tests for every main task.
   • Include E2E tests when the task spans frontend and backend or verifies a user workflow.
   • Reference relevant Tech Spec sections instead of repeating implementation details.

6. Report results.

   • Provide the final task summary path and individual task file paths.
   • Give a brief summary and wait for confirmation before any implementation work.

Hard Rules

• Do not create any task files before the user approves the high-level task list.
• Do not implement code.
• Do not create more than 10 main tasks unless the user explicitly approves it.
• Each main task must be a well-defined deliverable.
• Each main task must include tests that verify both functionality and business goal.
• Do not repeat implementation details already captured in the Tech Spec; reference techspec.md.

Quality Checklist

• PRD and Tech Spec were both reviewed.
• Applicable .codex/rules/ and .codex/skills/ entries were checked.
• High-level task list was shown to the user before file generation.
• User approved the high-level task list before files were written.
• tasks.md follows references/tasks-summary-template.md.
• Each individual task file follows references/individual-task-template.md.
• Every main task has unit and integration tests.
• Final response includes all saved paths and no implementation work was performed.