What is the benefit of the two-phase process?

The two-phase process allows you to review and approve the high-level roadmap (Parent Tasks) before the AI spends time generating every granular sub-task, ensuring accuracy.

Where does the skill save the generated tasks?

All task lists are saved as markdown files within a /tasks directory in your repository, using kebab-case for the filename.

Does it include testing in the task list?

Yes, Task Generator specifically identifies relevant test files and adds sub-tasks for unit testing alongside implementation requirements.

Can I use this for existing branches?

While it defaults to creating a new feature branch (task 0.0), you can explicitly opt out if you are already working on the target branch.

How do I trigger the Task Generator?

The skill will automatically prompt you after you exit specification mode, or you can explicitly request it after providing a plan or PRD.

Task Generator

Name: Task Generator
Author: Activer007

byActiver007

Productivity & Workflow

Generates structured, actionable markdown task lists from software specifications and technical requirements.

About

Task Generator streamlines the transition from planning to implementation by converting high-level specifications into detailed, step-by-step developer roadmaps. It follows a specialized two-phase process that first establishes high-level milestones and then breaks them down into granular, actionable sub-tasks, identifying relevant source and test files along the way. This skill ensures project consistency by enforcing a standardized markdown format and provides a clear path for developers to track their progress from branch creation to final testing.

Key Features

0 GitHub stars
Interactive 'Go' prompt to ensure alignment before detailed generation
Two-phase workflow for high-level planning and granular breakdown
Standardized Git branch initialization guidance
Identification of relevant source and unit test files for each task
Automated creation of structured markdown task files in /tasks directory

Use Cases

Onboarding junior developers with clear, imperative-style task instructions
Maintaining a standardized task tracking system within a code repository
Converting a Product Requirement Document (PRD) into a technical implementation plan

About

Key Features

0 GitHub stars
Interactive 'Go' prompt to ensure alignment before detailed generation
Two-phase workflow for high-level planning and granular breakdown
Standardized Git branch initialization guidance
Identification of relevant source and unit test files for each task
Automated creation of structured markdown task files in /tasks directory

Use Cases

Onboarding junior developers with clear, imperative-style task instructions
Maintaining a standardized task tracking system within a code repository
Converting a Product Requirement Document (PRD) into a technical implementation plan