Task Planner
- 19 installs
- 4 repo stars
- Updated December 6, 2025
- ajianaz/skills-collection
task-planner is a Claude skill that generates structured, step-by-step task lists from a spec, plan, or PRD as a checkable Markdown file.
About
This skill generates detailed, step-by-step task lists from a spec, plan, or PRD. A developer uses it after finishing a spec to break work into 5-7 parent tasks and then actionable sub-tasks, saved as a checkable Markdown file under /tasks/. It identifies relevant source and test files and targets a junior-developer audience so implementation is easy to follow.
- Generates structured task lists from specs, plans, or PRDs
- Two-phase flow: parent tasks first, then sub-tasks on confirmation
- Writes checkable task files to /tasks/ with relevant source and test files
Task Planner by the numbers
- 19 all-time installs (skills.sh)
- Ranked #2,032 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
task-planner capabilities & compatibility
- Capabilities
- writing plans · spec lean
- Use cases
- planning · project management
What task-planner says it does
Generate detailed, step-by-step task lists from specs, plans, or requirements.
Generate 5-7 high-level parent tasks:
npx skills add https://github.com/ajianaz/skills-collection --skill task-plannerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 19 |
|---|---|
| repo stars | ★ 4 |
| Last updated | December 6, 2025 |
| Repository | ajianaz/skills-collection ↗ |
What it does
Turn a spec, plan, or PRD into a structured, checkable task list of parent tasks and sub-tasks.
Who is it for?
Developers who want a spec or PRD broken into a checkable parent-and-sub-task implementation plan.
Skip if: Writing the spec itself or implementing the code.
When should I use this skill?
After completing a spec, when the user confirms or requests generating a task list from a plan, spec, or PRD.
What you get
- A /tasks/tasks-[feature-name].md file
- 5-7 parent tasks with sub-tasks
- List of relevant source and test files
By the numbers
- Generates 5-7 high-level parent tasks
- 2-phase process (parent tasks, then sub-tasks)
Files
Task Generator
Generate detailed, step-by-step task lists from specs, plans, or requirements.
Workflow (2-Phase Process)
Phase 1: Generate Parent Tasks
1. Analyze the spec/plan content for functional requirements and implementation scope 2. Create the task file at /tasks/tasks-[feature-name].md 3. Generate 5-7 high-level parent tasks:
- Always start with task 0.0: "Create feature branch" (unless user explicitly opts out)
- Use your judgment for the number of additional tasks
4. Present parent tasks to user in the output format (without sub-tasks) 5. Tell user: "I have generated the high-level tasks. Ready to generate sub-tasks? Reply Go to proceed."
Phase 2: Generate Sub-Tasks
1. Wait for user to reply "Go" 2. Break down each parent task into smaller, actionable sub-tasks 3. Identify relevant files to create/modify (include test files) 4. Update the task file with complete structure
Output Format
Save to /tasks/tasks-[feature-name].md:
## Relevant Files
- `path/to/file.ts` - Brief description of why this file is relevant
- `path/to/file.test.ts` - Unit tests for file.ts
- `path/to/component.tsx` - Component description
- `path/to/component.test.tsx` - Unit tests for component.tsx
### Notes
- Unit tests should be placed alongside the code files they test
- Use `npx jest [optional/path/to/test/file]` to run tests
## Instructions for Completing Tasks
**IMPORTANT:** As you complete each task, check it off by changing `- [ ]` to `- [x]`. Update after completing each sub-task.
## Tasks
- [ ] 0.0 Create feature branch
- [ ] 0.1 Create and checkout new branch (`git checkout -b feature/[feature-name]`)
- [ ] 1.0 [Parent Task Title]
- [ ] 1.1 [Sub-task description]
- [ ] 1.2 [Sub-task description]
- [ ] 2.0 [Parent Task Title]
- [ ] 2.1 [Sub-task description]Guidelines
- Target audience: Junior developer who will implement the feature
- Task style: Use imperative verbs (Create, Add, Implement, Update)
- Feature name: Derive from spec title/topic in kebab-case
- File identification: Include both source and test files
- Sub-task granularity: Each sub-task should be completable in one focused session
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
How does the two-phase process work?
Phase 1 generates 5-7 high-level parent tasks; Phase 2 waits for the user to reply Go, then breaks each into sub-tasks and identifies relevant files.
Where are task lists saved?
To /tasks/tasks-[feature-name].md as a checkable Markdown file.