create-tasks

/create-tasks

Decomposes a single requirement into discrete tasks and records them in the DevFlow database. Reviews are auto-spawned by the server for plan, build, test, and configure task types.

When to use

Run /create-tasks when a requirement is ready to be broken down into actionable units of work.

Steps

1. Identify the requirement — ask the user for a requirement_id, or call read_requirements to list open requirements and let the user choose.

2. Check existing tasks — call read_tasks filtered by requirement_id to see what already exists. Avoid inserting duplicates.

3. Decompose — analyse the requirement description and produce a list of tasks. For each task determine:

   • title: a short, action-oriented label (e.g. "Write init.sql schema")
   • task_type: one of plan, build, test, review, document, configure, research
   • status: always 'pending' for new tasks

4. Review-spawning rule — inform the user which tasks will auto-spawn a review:

   • Auto-spawns review: plan, build, test, configure
   • No review spawned: review, document, research

5. Insert tasks — call insert_task for each task. The server returns review_id alongside each inserted task row:

   • If review_id is not null, a review has been auto-spawned
   • If review_id is null, no review was spawned (expected for document, research, review types)

6. Report — summarise what was created:

   • Requirement ID and description
   • Table of inserted tasks: ID, title, task_type, status, review_id (if any)

Notes

• A single requirement can have tasks of mixed types (e.g. a build task and a test task).
• Never set task_type to a value outside the allowed enum: plan, build, test, review, document, configure, research.
• Do not call insert_review manually — the server handles auto-spawning.