task-list-generator

Generate phase-driven markdown task lists with parent and sub-tasks.

Updated Feb 7, 2023
One-click install
npx skills add https://github.com/simoneschiavo/simoneschiavo.github.io --skill task-list-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-list-generator
Source: https://github.com/simoneschiavo/simoneschiavo.github.io/tree/main/.claude/skills/task-list-generator
Command: npx skills add https://github.com/simoneschiavo/simoneschiavo.github.io --skill task-list-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates detailed, step-by-step task lists from user requirements, feature requests, or documentation. It guides developers through implementation with structured parent tasks and actionable sub-tasks.

Core Features & Use Cases

  • Phase-driven task generation: converts requirements into a hierarchical plan with 0.0 branch initiation and phased milestones.
  • Subtask orchestration: decomposes broad goals into concrete, testable actions with dependencies and sequencing.
  • Collaboration-ready output: produces markdown-ready task lists suitable for team workflows and progress tracking.

Quick Start

Provide your project requirements and the skill will output a structured, phase-driven task list with parent tasks and actionable subtasks.

Frequently Asked Questions about task-list-generator

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

FAQPage Schema
How do I generate a task list from software requirements and documentation?

To generate a task list from software requirements, provide your feature requests or documentation to the skill, which translates them into a structured, phase-driven markdown task list with parent tasks and actionable subtasks.

What is phase-driven task generation for project planning?

Phase-driven task generation is the process of converting broad project requirements into a hierarchical plan with phased milestones, starting with a canonical 0.0 branch initiation task to anchor the workflow.

Can I use this for engineering project planning and documentation review?

Yes, you can use this for engineering project planning and documentation review, as the skill applies structured task decomposition to translate technical needs into organized, testable work plans.

How do I break down broad project goals into actionable subtasks?

To break down broad project goals into actionable subtasks, the skill orchestrates dependencies and sequencing, decomposing high-level requirements into concrete, testable actions within a markdown-ready format.

What is the best way to create collaboration-ready task plans for development teams?

The best way to create collaboration-ready task plans is to process requirements into structured markdown task lists, which are suitable for team workflows and direct progress tracking.

Do I need to manually set up a 0.0 branch task for my workflow?

No, you do not need to manually set up a 0.0 branch task, as the skill automatically enforces a two-phase workflow that ensures a canonical 0.0 branch initiation task is included in the output.