create-tasks
/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).
- Author
- jagreehal ↗
- Repository
- jagreehal-claude-skills ↗
- Licence
- MIT
- Last repository change
- 30.07.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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).
Original author description
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).
How it works
- Critical rules
- Workflow
- Resources
- Validation
- Constraints
SKILL.md preview
--- name: create-tasks description: >- 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). version: 1.2.0 --- # 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`.
Files in this package (3)
- SKILL.md 2 KB
- references/slicing.md 2 KB
- references/template.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jagreehal/jagreehal-claude-skills | 100 | MIT |
| Heapy/kortex | 100 | Apache-2.0 |
| carloshpdoc/ios-workflow-claude | 100 | Apache-2.0 |
| sequenzia/agent-alchemy | 91 | MIT |
Database snapshot: 13.11.2026 · package version e32a8dffb776 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100planning-and-task-breakdown
Decompose specs into small, verifiable tasks with acceptance criteria and dependency ordering. Use when you have a spec and need implementable units. - 100planning-and-task-breakdown
Decompose specs into small, verifiable tasks with acceptance criteria and dependency ordering. Use when you have a spec and need implementable units. - 100plan-work
Break down an issue or task into concrete implementation steps with file locations, code changes, and acceptance criteria. Use when the user asks to "plan the implementation", "break down this task", "create an implementation plan", or needs a structured plan before coding. - 100writing-plans
Use when you have a spec, design doc, or requirements and need a detailed implementation plan before coding. Triggers: 'write a plan', 'create implementation plan', 'plan this out', 'break this down into steps', 'convert design to tasks', 'implementation order'. Also invoked by… - 90planning
Breaks a feature into ordered, verifiable tasks in a plan file and assigns a model per task. Use when the user asks for a plan, a task breakdown, or which model fits a plan task, or a change spans several files. Not for small edits or reviews. - 100plan-writing
Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.