What is the SPIDR technique mentioned in this skill?

SPIDR is a method for splitting user stories based on Paths, Interfaces, Data, Rules, and Spikes to ensure manageable task sizes.

How does this skill help with task estimations?

By enforcing the INVEST criteria and a 'max 1 day' rule, it ensures tasks are small enough for high-confidence estimation.

What is a vertical slice in this context?

A vertical slice is a task that touches all layers (UI, API, DB) for a specific sub-feature, ensuring it delivers demoable value.

Can it generate acceptance criteria?

Yes, it uses Example Mapping to create specific 'Given-When-Then' scenarios for every business rule identified.

Why should I use this over standard PRD summaries?

This skill avoids 'epic' traps by strictly splitting tasks into executable units that engineers can pick up without prior context.

Engineering Task Creator

Name: Engineering Task Creator
Author: NTCoding

byNTCoding

•

Productivity & Workflow

Transforms high-level requirements and PRDs into actionable, small-scale engineering tasks using industry-standard slicing techniques.

About

The Engineering Task Creator skill empowers Claude to act as a technical product manager, breaking down complex features into manageable vertical slices. By applying methodologies like SPIDR, Example Mapping, and INVEST criteria, it ensures every task is small enough to be completed in a single day and contains clear acceptance criteria in Given-When-Then format. This skill is essential for teams looking to improve sprint predictability, reduce ambiguity, and provide engineers with all the context needed to implement features without back-and-forth clarification.

Key Features

Enforces INVEST principles to ensure tasks are high-quality and estimable
Standardizes task documentation with specific verification and context sections
Implements SPIDR and Example Mapping for effective task slicing
Prioritizes vertical slices to deliver user value in every development unit
94 GitHub stars
Generates Given-When-Then acceptance criteria for clear testing

Use Cases

Splitting large, complex features into small, one-day vertical slices
Converting a high-level PRD into a backlog of actionable engineering tickets
Refining vague user stories into detailed, testable technical tasks

About

Key Features

Enforces INVEST principles to ensure tasks are high-quality and estimable
Standardizes task documentation with specific verification and context sections
Implements SPIDR and Example Mapping for effective task slicing
Prioritizes vertical slices to deliver user value in every development unit
94 GitHub stars
Generates Given-When-Then acceptance criteria for clear testing

Use Cases

Splitting large, complex features into small, one-day vertical slices
Converting a high-level PRD into a backlog of actionable engineering tickets
Refining vague user stories into detailed, testable technical tasks