# 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).

- Skill: `jagreehal/create-tasks` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add jagreehal/create-tasks`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jagreehal/create-tasks/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: jagreehal (https://skillmd.com/u/jagreehal)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/jagreehal/create-tasks

---


# 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](references/slicing.md) and [references/template.md](references/template.md).

## Workflow

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

## Resources

- [references/slicing.md](references/slicing.md) — Example Mapping, SPIDR, naming, INVEST. Read before creating tasks.
- [references/template.md](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`.