taskslisted

Turn an approved SPEC.md into a complete TASKS.md (phases, parallel tracks, dependency map), then create matching GitHub issues, a GitHub Project board, and empty-directory scaffolding from the spec's package layout. Use whenever the user invokes /ank:tasks, says "break this into tasks", "create the issues", "wire up the project board", or otherwise signals the approved spec should become trackable, parallel-friendly work. Requires a SPEC.md to exist and the user to have explicitly approved it. The skill HARD STOPS before creating GitHub side-effects, asks for confirmation, and gracefully degrades when the gh CLI is absent or unauthenticated.
ananthanandanan/skills · ★ 4 · AI & Automation · score 73

Install: claude install-skill ananthanandanan/skills

# Tasks The user has an approved `SPEC.md`. Your job is to turn it into: 1. A `TASKS.md` with phases, parallel tracks, sized tasks, dependencies, labels, and milestones. 2. One GitHub issue per task, with labels and dependency callouts in the body. 3. A GitHub Project board with issues grouped by milestone. 4. Empty directories matching the spec's package layout. You are **not** writing code. You are **not** scaffolding files inside the directories. You are not committing anything to git. ## Pipeline position ``` /ank:third-degree → /ank:spec → /ank:tasks → (build with Claude Code) → /ank:review-board (this) ``` This skill runs **only after** `SPEC.md` has been written and explicitly approved by the user. If there's no `SPEC.md` (root or `docs/spec/<slug>.md`), refuse and point at `/ank:spec`. If a `SPEC.md` exists but the conversation has no record of approval, ask once: "I see SPEC.md at `<path>` — has this been approved? Reply yes to proceed." ## Where TASKS.md lives Mirror the spec's location: | Spec location | Tasks location | |---|---| | `./SPEC.md` (product-level) | `./TASKS.md` | | `./docs/spec/<slug>.md` (feature-level) | `./docs/spec/<slug>.tasks.md` | If `TASKS.md` already exists, ask once before overwriting. ## TASKS.md shape Every TASKS.md the skill produces follows the same structure. Preserve all of these elements — they're what makes the file parallel-friendly and trackable: - **Phases** — Phase 0 setup