Taskify

Create tracker-neutral tasks that deliver coherent outcomes. A small batch may need no tasks: say so when decomposition adds no value, and leave the batch for direct implementation.

Establish the source

The project documents and their rules are in project-documents.md; its terms (authorized, obligation, lazy, pointer) apply throughout. Read the selected scope, applicable requirements and specifications, active working state, relevant code, domain vocabulary, and architectural decisions. Fetch the full body and comments of any referenced remote task.

Read configured tracker and task-writing conventions when present; local drafting works without tracker setup. Ask the user about material missing scope.

Decompose into outcomes

Prefer tracer bullets: narrow end-to-end slices that are independently demoable or verifiable, sized for a fresh implementation context. Group related work into a meaningful outcome rather than one task per layer or edit. Identify useful prefactoring before dependent feature slices.

For a wide mechanical refactor that cannot land in independent vertical slices, use expand-contract: introduce the new form compatibly, migrate bounded batches, then remove the old form after all migrations. If intermediate batches cannot stay green independently, state the integration branch and final integrate-and-verify dependency explicitly.

Every task must state: