task-planner

Generate structured parent and sub-tasks from specs into Markdown files.

4|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/ajianaz/skills-collection --skill task-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-planner
Source: https://github.com/ajianaz/skills-collection/tree/main/skills/task-planner
Command: npx skills add https://github.com/ajianaz/skills-collection --skill task-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts vague specs, requirements, or PRDs into structured, executable task lists, saving time during planning and reducing scope ambiguity.

Core Features & Use Cases

  • Parent task generation: Analyzes the spec to produce 5-7 high-level parent tasks.
  • Automated task file creation: Saves results to /tasks/tasks-[feature-name].md.
  • 2-phase workflow: Phase 1 creates parent tasks; Phase 2 breaks them into sub-tasks after user confirmation.
  • Traceable task structure: Produces clear task naming and actionable steps to guide implementation.

Quick Start

Paste your spec or PRD content and say "Generate tasks from this spec." I will return the high-level tasks and prompt you to proceed with sub-task generation.

Frequently Asked Questions about task-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a spec or requirements document into an actionable task list?

Task-planner converts specs into structured task lists by analyzing your requirements and generating 5-7 high-level parent tasks with corresponding sub-tasks. It saves the output to a markdown file, providing a clear roadmap for implementation.

What's included in the task list output?

The generated task list includes parent tasks (starting with creating a feature branch), sub-tasks with relevant file references, test requirements, and a two-phase workflow structure—Phase 1 presents parent tasks, Phase 2 breaks them into actionable steps suitable for junior developers.

Can I skip the initial feature branch task?

Yes. Task-planner defaults to including a 'Create feature branch' as the first task, but you can opt out if your workflow doesn't require it.

How does the two-phase workflow work?

Phase 1 analyzes your spec to create high-level parent tasks and saves them automatically. Phase 2 begins after you review Phase 1 and generates detailed sub-tasks, identifies affected files, and records test cases for each parent task.

What format should my spec or requirements be in?

Paste your spec, PRD, or requirements content directly—no specific format required. Task-planner accepts plain text descriptions and extracts the structure needed to generate tasks.

Where are the task lists saved?

Task lists are automatically saved to `/tasks/tasks-[feature-name].md`, keeping your planning artifacts organized and version-controllable alongside your codebase.