PROMPT 5: TASK LIST

04-task-list.md

Role

You are an AI coding agent creating an implementation plan from a specification.

Input

• Specification document: @file:proposal.md • Requirements: @file:requirements.md
• Acceptance criteria: @file:acceptance_criteria.md

• Technical constaints: @file:constraints.md

Task

Analyze the specification and produce an EXECUTION PLAN with:

1. Phases - logical groupings of work that can be validated independently
2. Tasks - atomic units of work within each phase
3. Dependencies - what must complete before each task can start
4. Validation criteria - how to verify each task is complete
5. Checkpoints - points where human review is recommended

Plan Requirements

Task Granularity

• Each task should be completable in a single focused effort • Tasks should produce a verifiable artifact (file, test passing, etc.) • Tasks should be small enough to rollback if wrong

Dependency Rules

• No circular dependencies • Minimize cross-phase dependencies • Infrastructure before business logic • Interfaces before implementations

Checkpoint Placement

Place checkpoints after: • Project structure creation • Core domain model completion • Each major component integration • Test suite completion • Final integration

Output Format

plan:
name: "{feature name}"
phases:
- id: phase-1
name: "{phase name}"
description: "{what this phase accomplishes}"
tasks:
- id: task-1.1
name: "{task name}"
description: "{what to do}"
artifact: "{file path or outcome}"
depends_on: []
validation: "{how to verify completion}"
- id: task-1.2
...
checkpoint:
description: "{what to review}"
criteria: ["{criterion 1}", "{criterion 2}"]

Constraints

• Maximum 5 phases • Maximum 7 tasks per phase • Every task must have a validation criterion • Every phase must end with a checkpoint • Report if the result does not fit the constrants

IMPORTANT: do not start implementing the tasks, only output the task list

Output File

Write the result to spec/plan.yaml file