create-tasks

Break down product requirements into INVEST-compliant tasks for sprint planning.

1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/michelve/hugin-cowork --skill create-tasks-michelve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-tasks
Source: https://github.com/michelve/hugin-cowork/tree/main/skills/create-tasks
Command: npx skills add https://github.com/michelve/hugin-cowork --skill create-tasks-michelve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms broad requirements or product descriptions into well-defined, actionable tasks that engineers can implement efficiently, ensuring clarity and reducing ambiguity.

Core Features & Use Cases

  • Task Definition: Creates tasks with clear deliverables, context, acceptance criteria, and dependencies.
  • Requirement Breakdown: Utilizes techniques like Example Mapping and SPIDR to split large requirements into manageable, vertical slices.
  • Use Case: You have a new feature request in a PRD. Use this Skill to break it down into individual tasks for the development backlog, each adhering to INVEST principles.

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 product requirements into actionable tasks for sprint planning?

To break down product requirements for sprint planning, you transform broad descriptions into well-defined tasks using techniques like Example Mapping and SPIDR. This ensures each task is a manageable, vertical slice ready for implementation.

What is the SPIDR technique for requirements breakdown?

The SPIDR technique is a method for splitting large epics into smaller, manageable units. It helps ensure that requirements breakdown results in clear deliverables and context, reducing ambiguity for engineers during sprint planning.

How do I ensure my backlog tasks are INVEST-compliant?

To ensure backlog tasks are INVEST-compliant, apply structured breakdown techniques like Example Mapping to your requirements. This process creates vertically sliced tasks that adhere to INVEST principles, complete with clear acceptance criteria and dependencies.

Can I use this task creation process for agile project management without external dependencies?

Yes, you can use this task creation process for agile project management without external dependencies. The breakdown mechanism operates independently but requires adherence to your project-specific task storage conventions and naming patterns.

What is the best way to split a large epic into smaller, manageable tasks?

The best way to split a large epic into smaller tasks is using Example Mapping and SPIDR techniques. This approach creates vertically sliced, actionable tasks with clear deliverables, context, and dependencies for your development backlog.

When should I not use automated task breakdown for my development backlog?

You should avoid automated task breakdown for your development backlog when your project lacks specific task storage conventions or naming patterns. The process requires these predefined project structures to generate well-formed tasks accurately.