What is a vertical slice in task creation?

A vertical slice is a work item that cuts through all layers of a system (UI, API, and Database) for a single specific feature, ensuring it is demoable and provides value upon completion.

Why is there a one-day limit on task size?

Limiting tasks to one day of work reduces project risk, provides faster feedback loops, and makes progress more predictable and easier to track for engineering teams.

What criteria does a task need to be 'engineer-ready'?

A task is ready if it includes clear deliverables, the 'why' behind the work, key decisions, acceptance criteria, dependencies, related code patterns, and verification steps.

How does the SPIDR technique help with tasks?

SPIDR is a framework for splitting large stories based on Paths, Interfaces, Data, Rules, and Spikes. It ensures complex features are broken down into small, manageable units.

Agile Task Architect

Name: Agile Task Architect
Author: NTCoding

byNTCoding

•

Productivity & Workflow

Transforms complex requirements and PRDs into small, actionable vertical slices using industry-standard agile methodologies.

About

The Agile Task Architect skill empowers teams to transform vague project requirements or lengthy Product Requirement Documents (PRDs) into high-quality, implementable tasks. It enforces rigorous standards like the INVEST criteria and SPIDR splitting techniques to ensure every task is a vertical slice deliverable in under a day. By providing engineers with comprehensive context, clear acceptance criteria, and specific verification steps, this skill eliminates ambiguity and reduces the need for back-and-forth communication during the development cycle.

Key Features

Example Mapping checks to uncover hidden unknowns and business rules
Standardized Markdown templates for consistent engineering documentation
SPIDR-based task splitting to break down epics into manageable chunks
Vertical slice enforcement to ensure value delivery across all stack layers
INVEST validation to confirm tasks are independent, small, and testable
78 GitHub stars

Use Cases

Breaking down a PRD into a backlog of ready-to-code development tickets
Defining sprint work items that are guaranteed to fit within a single day of work
Converting complex feature requests into specific, action-oriented technical tasks

About

Key Features

Example Mapping checks to uncover hidden unknowns and business rules
Standardized Markdown templates for consistent engineering documentation
SPIDR-based task splitting to break down epics into manageable chunks
Vertical slice enforcement to ensure value delivery across all stack layers
INVEST validation to confirm tasks are independent, small, and testable
78 GitHub stars

Use Cases

Breaking down a PRD into a backlog of ready-to-code development tickets
Defining sprint work items that are guaranteed to fit within a single day of work
Converting complex feature requests into specific, action-oriented technical tasks