create-tasks

Name: create-tasks
Availability: InStock
Author: igoyetche

Generate actionable engineering tasks from PRDs using SPIDR and INVEST.

Updated Mar 3, 2026

Search Tags:#project management #software engineering #task management #sprint planning #agile development #requirements breakdown

Ready to run

npx skills add https://github.com/igoyetche/send-to-kindle --skill create-tasks-igoyetche

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-tasks
Source: https://github.com/igoyetche/send-to-kindle/tree/main/.claude/skills/create-tasks
Command: npx skills add https://github.com/igoyetche/send-to-kindle --skill create-tasks-igoyetche

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms high-level requirements or feature descriptions into well-defined, actionable tasks that engineers can implement without needing extensive prior context.

Core Features & Use Cases

Task Decomposition: Splits large requirements into smaller, manageable tasks using techniques like SPIDR.
Structured Task Creation: Ensures tasks include all necessary information: deliverable, context, decisions, acceptance criteria, dependencies, and related code.
Use Case: A product manager provides a PRD for a new feature. This Skill breaks down the feature into individual tasks, each with clear acceptance criteria and context, ready for the engineering team to pick up.

Quick Start

Use the create tasks skill to break down the following requirement into actionable tasks: "Implement user profile editing functionality."

Frequently Asked Questions about create-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I break down high-level requirements into actionable engineering tasks?▼

Break down high-level requirements by decomposing work using Example Mapping and SPIDR techniques. This process ensures each engineering task forms a vertical slice with clear deliverables, context, acceptance criteria, dependencies, and verification steps.

What is the best way to structure tasks for agile sprint planning?▼

The best way to structure tasks for agile sprint planning is to apply INVEST principles to ensure proper task sizing and quality. Each task should contain structured information like deliverables, context, decisions, and clear acceptance criteria.

How does SPIDR technique work for software engineering task decomposition?▼

The SPIDR technique works for software engineering task decomposition by splitting large requirements into smaller, manageable tasks. It ensures each resulting task is a vertical slice with well-defined context, dependencies, and verification steps.

Can I generate tasks directly from a PRD for my development team?▼

Yes, you can generate tasks directly from a PRD. The system transforms high-level requirements or feature descriptions into well-defined, actionable tasks that engineers can implement without needing extensive prior context.

What should be included in actionable engineering tasks to avoid missing context?▼

Actionable engineering tasks should include the deliverable, context, decisions, acceptance criteria, dependencies, and related code. This structured task creation prevents engineers from needing extensive prior context to implement the work.

When should I not use automated task decomposition for project management?▼

Automated task decomposition may not be suitable when high-level requirements lack sufficient detail for Example Mapping, or when a project requires horizontal architectural slicing instead of vertical feature slices adhering to INVEST principles.