task-generation

Generate parent tasks from a PRP and output a tasks.md file.

15|2|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/aspiers/ai-config --skill task-generation-aspiers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-generation
Source: https://github.com/aspiers/ai-config/tree/main/.claude/skills/task-generation
Command: npx skills add https://github.com/aspiers/ai-config --skill task-generation-aspiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a Product Requirements Prompt (PRP) into a ready-to-implement task backlog, reducing planning time and ensuring alignment between product and engineering teams.

Core Features & Use Cases

  • Generate 3-8 high-level parent tasks from a PRP to scaffold implementation planning.
  • Pause for user confirmation before generating sub-tasks to ensure alignment.
  • Output a .ai/[feature-name]/tasks.md file with tasks, relevant files, and a commit message template.
  • Support a two-phase workflow for task planning and execution.

Quick Start

Provide the PRP location (e.g., .ai/[feature-name]/prp.md) and I will generate the parent tasks.

Frequently Asked Questions about task-generation

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

FAQPage Schema
How do I generate an actionable task list from a product requirements prompt?

To generate a task list from a product requirements prompt, you provide the PRP location to automate a structured work breakdown. The tool creates 3-8 high-level parent tasks and outputs a tasks.md file with relevant files and a commit message template.

Can I review parent tasks before sub-tasks are generated for my project?

Yes, you can review parent tasks before sub-tasks are generated. The workflow explicitly pauses for user confirmation after scaffolding the initial 3-8 parent tasks to ensure alignment before detailing the subsequent sub-tasks.

What is the best way to automate work breakdown structure for agile planning?

Automating work breakdown structure for agile planning involves converting a PRP file into a ready-to-implement task backlog. This approach reduces planning time and ensures alignment between product and engineering teams through a structured two-phase workflow.

Does the task generation workflow output a commit message template?

Yes, the task generation workflow outputs a commit message template. The generated tasks.md file includes clearly formatted tasks, relevant files for implementation, and a commit message template to accelerate the execution phase.

Where should my PRP file be located to use automated task breakdown?

Your PRP file should be located at .ai/[feature-name]/prp.md to use automated task breakdown. Providing this specific PRP location allows the system to parse the product requirements and generate the corresponding parent tasks.

Why use a two-phase workflow for project task planning?

A two-phase workflow for project task planning separates high-level scaffolding from detailed sub-task generation. This enforces an explicit confirmation pause, ensuring the generated task backlog aligns with product requirements before implementation planning proceeds.