create-tasks

Converts PRDs into task-ready work items using Example Mapping and SPIDR.

3|1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/jagreehal/jagreehal-claude-skills --skill create-tasks-jagreehal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-tasks
Source: https://github.com/jagreehal/jagreehal-claude-skills/tree/main/skills/create-tasks
Command: npx skills add https://github.com/jagreehal/jagreehal-claude-skills --skill create-tasks-jagreehal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams convert ambiguous requirements and PRDs into well-scoped, task-ready work items. It ensures engineers and product stakeholders share a clear understanding of deliverables, context, and criteria, reducing back-and-forth.

Core Features & Use Cases

  • Delivers a concrete, action-oriented task template that captures deliverables, context, decisions, acceptance criteria, dependencies, and related code.
  • Supports Example Mapping and SPIDR-based splitting to keep tasks small, focused, and vertically sliced across product, API, and UI layers.
  • Guides teams in applying INVEST criteria to keep tasks independent, valuable, estimable, small, and testable.

Quick Start

To create a task, start from a PRD or requirement, apply Example Mapping to produce a single, vertical slice, and fill in the Task Template with acceptance criteria.

Frequently Asked Questions about create-tasks

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

FAQPage Schema
How do I turn PRD requirements into actionable task-ready work items?

To create vertical-slice tasks from requirements, apply Example Mapping and SPIDR techniques to split work across UI, API, and backend layers. This produces focused, task-ready work items complete with context, acceptance criteria, and dependencies.

What is Example Mapping and how does it help slice product requirements?

Example Mapping is a technique to slice product requirements into single, vertical deliverables spanning UI, API, and backend. It helps teams discover rules and acceptance criteria by extracting concrete examples from PRDs, ensuring shared understanding before development.

How do I apply INVEST criteria when splitting tasks from a PRD?

To apply INVEST criteria when splitting tasks from a PRD, evaluate each generated work item for independence, negotiability, value, estimability, smallness, and testability. This ensures tasks remain small, focused, and vertically sliced across product layers.

Does this approach to task creation work without a full PRD document?

Yes, this task creation approach works without a full PRD document. It guides engineers to craft precise work items from any requirements, using Example Mapping to extract context and SPIDR to enforce one-delivery scope across UI, API, and backend.

What is the best way to structure a task template for vertical slices?

The best way to structure a task template for vertical slices is to capture deliverables, context, decisions, acceptance criteria, dependencies, and related code. This template aligns with workflow practices like tasks.md and session.md for cross-functional delivery.