create-tasks
Create Tasks
A task file is the unit an AI agent picks up and ships. Each file has a checkbox list of work items with concrete file paths and a code-verifiable acceptance list that always includes a test command. The consuming AI ticks checkboxes as it completes them — anything a human has to look at by hand is forbidden.
When to use
- A slice exists with §3 decisions resolved and §7 empty (or closed).
- A feature needs to be queued for agent execution.
- You need a verifiable handoff between planning and implementation.
When NOT to use
- The slice has open decisions or open questions — finish the slice first.
- The change is a single-line edit — just edit it.
- The slice's HOW is still genuinely uncertain — go back to
/sliceand resolve it.
Output location
Mirror the existing repo convention. Tasks pool by feature, not by slice.
More from patrickruddiman/skills
spec
Write a detailed, objective specification of WHAT a system does and WHY. No code, no file paths, no library picks, no implementation prescriptions of any kind. The spec is read by an AI coding agent that will produce its own plan; the spec exists to bound the problem completely — every user-visible behavior, persona task, lifecycle transition, and failure mode.
10slice
Produce a scoped design doc for one technical vertical of a parent spec. Researches the existing codebase first, surfaces implementation choices as questions one at a time, and only drafts the doc after the user resolves them. No code, no tasks — design only.
9hunt
Aggressively debug, diagnose, or root-cause an issue. Drives a disciplined hunt — query telemetry, reproduce, bisect, instrument, hypothesize-test-confirm, and verify causation by reverting the fix. Refuses common anti-patterns (fix-without-repro, symptom suppression, multi-variable changes, theorize-without-running). Use when the user types /hunt or asks to debug, diagnose, root-cause, track down, or figure out a bug, crash, regression, flaky test, or unexplained behavior.
7worktree
Create or enter a git worktree for the current repo. New worktrees are named repo-<slug>, placed as a sibling of the repo root, and check out a branch (existing or new). Use when the user says "/worktree", "spin up a worktree", "branch off into a worktree", "hop into worktree X", or wants to work on a separate branch in parallel without disturbing the current checkout.
6schedule
Schedule a one-shot task (Windows/Linux/macOS) to run a command or prompt at a specific time or after a delay. Use when the user says "schedule", "/schedule", "in N minutes/seconds run", "at HH:MM run", "remind me to run", "queue this for later", or wants a task to fire reliably while they step away.
6best-practice
Align a repo or branch with current coding best practices — detect divergences from project conventions and the industry baseline (tests, types, error handling at boundaries, naming, security, observability, documentation), then apply alignment changes one type per commit with tests staying green throughout. Produces commits, not reports. Use when the user says "/best-practice", "align this branch", "best practices pass", "bring this repo up to standard", "fix conventions across this branch", "what's missing from best practices".
4