task-slicer

Split features into atomic 2–4h tasks with independent tests and minimal dependencies

⭐1stars🔀0forks📁View on GitHub🕐Updated Nov 10, 2025

When & Why to Use This Skill

The Task Slicer skill is a specialized tool designed to bridge the gap between high-level feature requirements and technical execution. It automates the process of decomposing complex user stories into granular, atomic tasks (2–4 hours each) with a focus on testability and minimal dependencies. This ensures a streamlined development workflow, more accurate project estimations, and improved delivery predictability for agile teams and AI-driven development pipelines.

Use Cases

  • Agile Sprint Planning: Automatically transform vague user stories into a structured backlog of actionable tasks, complete with time estimates and test focuses.
  • Developer Handoffs: Generate standardized task files (TASK-US-xxx.md) that provide clear inputs, outputs, and dependencies for individual contributors.
  • AI Agent Orchestration: Use as a pre-processing step for autonomous coding agents to ensure they receive manageable, well-defined sub-tasks rather than overwhelming feature requests.
  • Project Estimation & Scoping: Quickly assess the complexity of a new feature by breaking it down into measurable time blocks to identify potential bottlenecks early.
nametask-slicer
descriptionSplit features into atomic 2–4h tasks with independent tests and minimal dependencies
version0.1.0
tags[planning, tasks]

Task Slicer

Purpose

Turn a user story into small, testable tasks with clear inputs/outputs.

Behavior

  1. Create 3–10 tasks, each 2–4 hours.
  2. For each task: description, files, test focus, dependencies, estimate.
  3. Name files TASK-US-<id>-<n>.md and reference the story ID.

Guardrails

  • Prefer independence; minimize cross-task dependencies.
  • Split or merge tasks to hit target size.

Integration

  • Project Manager agent; /lazy create-feature task generation step.

Example Prompt

Slice US-20251027-001 into executable tasks.