Task Slicer

Slicing Rules

Prefer:

• user-visible end-to-end increments
• thin slices that exercise multiple layers only when needed
• tasks that can be owned and verified independently
• slices whose REQ-* and SCN-* coverage can be verified without guesswork

Avoid:

• pure layer splits with no user outcome
• giant umbrella tasks
• tasks that require hidden context from other slices

Parallel Group Rules

Assign a simple parallel group label when useful:

• G1, G2, G3

Only group tasks in parallel when:

• they do not mutate the same contract
• they do not depend on the same unfinished artifact
• their verification can run independently

Handoff Quality Bar

A good task file allows an implementation agent to start work with:

• no extra planning
• no scope invention
• a clear completion test
• explicit traceability targets for completion gating

References

• .claude/docs/guidelines/product-definition-workflow.md
• .claude/templates/product-definition/task.template.md