jagreehal 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.mdviasession-continuity.