do-create-tasks

Create incremental task plans from PRD and Tech Spec documents.

28|1|Updated Apr 5, 2026

Search Tags:#workflow #documentation #prd #project-management #tests #techspec #task-planning

Ready to run

npx skills add https://github.com/fabio-barboza/development-orchestrator --skill do-create-tasks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: do-create-tasks
Source: https://github.com/fabio-barboza/development-orchestrator/tree/main/skills/do-create-tasks
Command: npx skills add https://github.com/fabio-barboza/development-orchestrator --skill do-create-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps teams convert PRD and Tech Spec documents into a structured, incremental task plan. It outputs a tasks.md and individual task files, enabling traceable, testable delivery and reducing ambiguity.

Core Features & Use Cases

Convert PRD and Tech Spec into a sequenced list of implementation tasks, each with its own test suite.
Generate outputs at ./prds/prd-[feature-slug]/tasks/ including tasks.md and <number>_task.md files.
Enforce the project structure and naming conventions, and present a high-level task list for user approval before file creation.

Quick Start

Forneça o slug do PRD e Tech Spec para iniciar a geração da lista de tarefas para aprovação.

Frequently Asked Questions about do-create-tasks

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

FAQPage Schema

How do I break a PRD and Tech Spec into actionable development tasks?▼

To break a PRD and Tech Spec into actionable tasks, provide the feature slug to generate a structured, incremental task plan. The system creates a tasks.md file and individual numbered task files with clear dependencies and test suites for user approval.

What is the best way to structure implementation tasks with unit and integration tests?▼

Structuring implementation tasks with tests involves generating a sequenced list of executable steps directly from project documentation. This creates traceable task files that enforce directory structure and naming rules while including specific unit and integration test requirements.

How do I generate a task plan from project documentation without runtime execution?▼

Generating a task plan without runtime execution requires parsing PRD and Tech Spec documents to produce static markdown files. The system outputs a high-level task list for explicit user approval before creating any files, ensuring no code is executed during planning.

Can I enforce specific directory structures and file naming conventions for task planning?▼

Yes, you can enforce specific directory structures and file naming conventions for task planning. The system automatically generates outputs under a strict ./prds/prd-[feature-slug]/tasks/ path, creating a tasks.md file and numbered _task.md files to maintain project consistency.

Do I need to approve the task list before individual task files are created?▼

Yes, user approval is required before individual task files are created. The system first presents a high-level task list generated from the PRD and Tech Spec, waiting for your confirmation before writing the tasks.md and numbered task files to the directory.