What is the ideal task size for Task Slicer?

Task Slicer is configured to break features into 'atomic' tasks that typically take between 2 and 4 hours to complete, making them easy to track and finish in a single session.

Can Task Slicer help with task dependencies?

One of the core guardrails of the skill is to prefer independence and minimize cross-task dependencies, allowing developers to work on different parts of a feature with minimal friction.

Does Task Slicer create documentation?

Yes, it creates standardized markdown files following the naming convention TASK-US- - .md, which can be checked into your repository for project tracking.

How does Task Slicer handle testing?

Every task generated by the skill includes a specific 'test focus' area, ensuring that each unit of work is independently verifiable and compatible with test-driven development.

Task Slicer

Name: Task Slicer
Author: MacroMan5

byMacroMan5

•

Productivity & Workflow

Deconstructs complex user stories into small, testable, 2-4 hour atomic tasks to streamline development workflows.

About

Task Slicer is a specialized Claude Code skill designed to optimize the planning phase of software development by breaking down large features into manageable, actionable chunks. It automatically generates a series of 3-10 independent tasks, each complete with its own description, file references, and specific test focus, ensuring that every piece of work is estimable and verifiable. By enforcing a 2-4 hour execution window and minimizing cross-task dependencies, this skill helps developers maintain high momentum and implement features through a structured, test-driven approach.

Key Features

2 GitHub stars
Creates standardized markdown documentation for task tracking
Defines independent test focuses for every task unit
Generates 3-10 atomic tasks per feature
Targets a consistent 2-4 hour execution window for better estimation
Minimizes cross-task dependencies to enable parallel work

Use Cases

Establishing a test-driven development roadmap for a specific project requirement
Breaking down a complex user story into an actionable technical sprint plan
Generating granular estimates for new feature implementations

About

Key Features

2 GitHub stars
Creates standardized markdown documentation for task tracking
Defines independent test focuses for every task unit
Generates 3-10 atomic tasks per feature
Targets a consistent 2-4 hour execution window for better estimation
Minimizes cross-task dependencies to enable parallel work

Use Cases

Establishing a test-driven development roadmap for a specific project requirement
Breaking down a complex user story into an actionable technical sprint plan
Generating granular estimates for new feature implementations