generate-task-breakdown

Generate executable development tasks with acceptance criteria from product requirements and architecture documentation.

Updated Feb 11, 2026

Search Tags:#project planning #task breakdown #acceptance criteria #agile #progress tracking #scrum #development roadmap

Ready to run

npx skills add https://github.com/juniorfontenele/ai-guidelines --skill generate-task-breakdown-juniorfontenele

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate-task-breakdown
Source: https://github.com/juniorfontenele/ai-guidelines/tree/main/.agents/skills/generate-task-breakdown
Command: npx skills add https://github.com/juniorfontenele/ai-guidelines --skill generate-task-breakdown-juniorfontenele

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill transforms complex product requirements and architecture documents into a clear, actionable plan of development tasks, ensuring no detail is missed and progress is trackable.

Core Features & Use Cases

Task Generation: Breaks down large features into small, manageable tasks with acceptance criteria.
Progress Tracking Setup: Creates structured files for monitoring task status, commits, and blockers.
Use Case: You have a new feature defined in your PRD. Use this Skill to generate a detailed list of all development tasks, including models, services, and UI components, along with acceptance criteria and a progress tracking template.

Quick Start

Use the generate-task-breakdown skill to create a task breakdown for the new user authentication feature.

Frequently Asked Questions about generate-task-breakdown

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

FAQPage Schema

How do I generate development tasks from product requirements?▼

To generate development tasks from product requirements, this skill transforms your PRD and architecture documents into organized epics and manageable tasks with acceptance criteria. It outputs structured task lists directly into your docs/tasks/ directory.

What is the best way to break down large features into manageable tasks?▼

The best way to break down large features into manageable tasks is by parsing product requirements to generate specific models, services, and UI components. This approach ensures every generated task includes clear acceptance criteria for agile development.

How does progress tracking work for agile development roadmaps?▼

Progress tracking for development roadmaps works by creating structured files in docs/progress/ that monitor task status, commits, and blockers. This mechanism ensures your implementation plan remains trackable throughout the development lifecycle.

Can I use this task breakdown approach for Scrum project planning?▼

Yes, you can use this task breakdown approach for Scrum project planning because it structures work into epics and tasks with acceptance criteria. It supports agile methodologies by creating structured task lists and progress tracking files.

Do I need architecture documentation to create a development roadmap?▼

Yes, you need architecture documentation and product requirements to create a development roadmap. The skill relies on these input documents to accurately organize work into epics and generate executable development tasks.