Verified:GitHub

wa:dev-plan

Generate dependency-aware implementation task plans from FRD acceptance criteria.

Updated Mar 26, 2026

Search Tags:#acceptance criteria #task planning #dependency graph #docs generation #tracker integration #development rigor

Ready to run

npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wa:dev-plan
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/dev-plan
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts feature design and acceptance criteria into an executable, dependency-aware implementation task plan so teams can move from specs to delivery without guessing.

Core Features & Use Cases

AC-ID driven task breakdown: Derives tasks that map directly to FRD.md acceptance criteria (AC-IDs), including complexity estimates.
Dependency and wave planning: Builds a valid dependency graph (e.g., database → backend API → frontend; integration and test tasks sequenced appropriately).
Tracker issue creation and task registration: Creates epic and task issues in the configured tracker (or generates local keys when tracker integration is not configured), and registers tasks for progress visibility.
User approval workflow: Presents a structured wave plan and iterates until the breakdown is explicitly approved.

Quick Start

Run the command /dev-plan user notification preferences to generate docs/{feature}/TASKS.md from your FRD and design artifacts.

Frequently Asked Questions about wa:dev-plan

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

FAQPage Schema

What is the best way to create a dependency graph for feature planning?▼

Dependency graph creation for feature planning sequences tasks by mapping FRD acceptance criteria to components. It structures waves like database to backend API to frontend, ensuring valid execution order before delivery.

Do I need an FRD.md file to generate a task breakdown?▼

Yes, you need an FRD.md file containing acceptance criteria to generate a task breakdown. Optional design, architecture, and QA-PLAN.md documents further inform component work mapping, dependency derivation, and test task sequencing.

Can I create tracker issues automatically from a task plan?▼

Yes, you can create tracker issues automatically from a task plan via tracker:router and tracker:issue-create. If tracker integration is not configured, it generates local keys and registers tasks locally for progress visibility.

How does user approval workflow function during task breakdown generation?▼

User approval workflow presents a structured wave plan during task breakdown generation and iterates until the breakdown is explicitly approved. This ensures the derived task dependencies and component mappings meet requirements before finalizing.