plan-task

Convert vague feature requests into wave-based plans with task-file mappings.

20|3|Updated Apr 30, 2026

Search Tags:#verification #plan #dependency-graph #task-planning #feature-management #wave-planning

Ready to run

npx skills add https://github.com/DVNghiem/FlowDeck --skill plan-task-dvnghiem

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-task
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/plan-task
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill plan-task-dvnghiem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down vague feature requests into concrete, executable plans that can be traced and verified.

Core Features & Use Cases

Maps requirements to discrete tasks and files
Builds a dependency graph and wave-based execution plan
Enforces observable success criteria and per-task verification

Quick Start

Instruct the AI to convert a user story into a wave-based plan with tasks mapped to files and defined success criteria.

Frequently Asked Questions about plan-task

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

FAQPage Schema

How do I break down a vague feature request into executable task plans?▼

To break down a vague feature request into executable task plans, you convert user stories into a wave-based execution format. This maps discrete tasks to specific files and enforces observable success criteria for multi-file feature work.

What is wave-based planning for multi-file feature development?▼

Wave-based planning organizes feature development into sequential execution waves. It builds a dependency graph to coordinate multiple contributors across different modules, ensuring tasks are executed in the correct order with verifiable success criteria.

How do I map feature requirements to discrete tasks and source files?▼

You can map feature requirements to discrete tasks and source files by structuring the plan to explicitly associate each task with specific modules. This ensures every task has defined dependencies, observable success criteria, and explicit verification steps.

Can I coordinate dependencies and parallel work streams across multiple contributors?▼

Yes, you can coordinate dependencies and parallel work streams by generating a dependency graph that defines execution waves. This allows multiple contributors to work on separate files concurrently while maintaining verifiable integration points.

When do I need a dependency graph for task planning?▼

You need a dependency graph for task planning when handling multi-file feature work where execution order matters. It prevents integration conflicts by mapping task dependencies and organizing them into verifiable, wave-based execution phases.