Create tasks

Skill jagreehal/jagreehal-claude-skills/skills/create-tasks

Breaks work into concrete, verifiable tasks with clear done criteria and ordering. Use this skill when turning an approved plan or ambiguous request into an executable task list before coding. Do not use when/for designing product requirements (use design-exploration) or writing the full implementation plan with copy-pasteable code (use implementation-planning).From its SKILL.md

Install

npx -y skills add jagreehal/jagreehal-claude-skills --skill create-tasks

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, as published. Nobody here has run it

Create Tasks

Critical rules

Never create a task without validating size first. A PRD deliverable is often an epic.
Never copy PRD bullets verbatim — use Example Mapping (story/rules/examples/questions).
Vertical slices only (one specific thing through all needed layers). Max 1 day. Must pass INVEST.
Every task: deliverable, why, decisions, Given-When-Then AC, deps, related code, verification.
Follow project task/docs conventions; ask and document if unclear.
Before slicing or filling the template, read references/slicing.md and references/template.md.

Workflow

Slice with Example Mapping; apply SPIDR on split signals.
Write acceptance criteria as Given-When-Then (happy/edge/error).
Name with [Action] [object] [constraint]; reject epic naming patterns.
Validate INVEST and vertical-slice limits.
Fill the task template (context paths/URLs required).
Checkpoint: size, name, vertical, INVEST, cold-start implementability.

Resources

references/slicing.md — Example Mapping, SPIDR, naming, INVEST. Read before creating tasks.
references/template.md — task template and process checklist. Read when writing the task body.

Validation

≤1 day, vertical, INVEST pass
Specific action-oriented title (no "and" / "full implementation")
Given-When-Then AC; referenced docs have paths/URLs
Engineer can implement without asking questions

Constraints

Skip for single-file obvious scope or already day-sized tasks.
Related: implementation-planning, session-continuity, tdd-workflow, testing-strategy.
Definitions only; execution tracking may use .claude/tasks.md via session-continuity.