task-planner

Decompose requirements documents into phases, tasks, and subtasks.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/vuthuonghai-steve/KLTN-By_Thuong_Hai-Steve --skill task-planner-vuthuonghai-steve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-planner
Source: https://github.com/vuthuonghai-steve/KLTN-By_Thuong_Hai-Steve/tree/main/.agent/skills/task-planner
Command: npx skills add https://github.com/vuthuonghai-steve/KLTN-By_Thuong_Hai-Steve --skill task-planner-vuthuonghai-steve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill transforms complex requirements or research documents into structured, actionable task plans, eliminating ambiguity and providing a clear roadmap for development.

Core Features & Use Cases

  • Decomposition: Breaks down features into phases, tasks, and subtasks.
  • Structured Planning: Generates clean planning documents without code examples, focusing on logic and business rules.
  • Use Case: When presented with a new feature request, this Skill will create a detailed plan outlining all necessary phases, tasks, and subtasks, ready for the development team.

Quick Start

Use the task-planner skill to break down the requirement document 'new-feature-spec.md' into phases and tasks.

Frequently Asked Questions about task-planner

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

FAQPage Schema
How do I break down complex project requirements into actionable tasks?

Task decomposition transforms complex requirement documents into structured planning artifacts by defining phases, tasks, and subtasks. It eliminates ambiguity by generating a clear roadmap with logical steps and business rules for development teams.

What is the best way to create a project roadmap from a feature specification?

The best way to create a project roadmap from a feature specification is by decomposing the requirements into logical steps and business rules. This generates clean planning artifacts focused on project management logic rather than code implementation.

Can I generate a development plan that excludes code samples and focuses on business rules?

Yes, you can generate a development plan that excludes code samples. This task planning process focuses strictly on defining logical steps and business rules, ensuring the output remains a clean planning document rather than an implementation guide.

Does task decomposition work with external research documents for requirements analysis?

Task decomposition works with external research documents by utilizing web fetching and code exploration tools to gather context. This allows the process to refine plans and extract structured phases from the provided requirements analysis documents.

What are the limitations of using automated task planning for project management?

A limitation of automated task planning is that it generates structured phases and tasks but explicitly excludes code samples. It focuses purely on requirements analysis and logical roadmapping, so it cannot directly provide implementation scripts for development.