project-planner

Decompose fuzzy goals into a WBS with milestones, dependencies, and effort estimates.

3|2|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JayRHa/AgentSkills --skill project-planner-jayrha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-planner
Source: https://github.com/JayRHa/AgentSkills/tree/main/project-planner
Command: npx skills add https://github.com/JayRHa/AgentSkills --skill project-planner-jayrha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Decomposes fuzzy goals into a structured plan that yields a Work Breakdown Structure (WBS), milestones, dependencies, and defensible effort estimates, enabling teams to plan, track, and execute projects with clarity.

Core Features & Use Cases

  • Generate a deliverable-oriented WBS with clearly defined leaf tasks (8–80 hours each) to support accurate estimation and assignment.
  • Map milestones and inter-task dependencies to create a coherent schedule and identify the critical path.
  • Produce a ready-to-fill project plan (templates/project-plan.md) including the risk register to support governance and review.

Quick Start

Provide a goal and constraints; the skill will generate a complete project plan with WBS, milestones, dependencies, estimates, and a schedule.

Frequently Asked Questions about project-planner

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

FAQPage Schema
How do I turn fuzzy project goals into a Work Breakdown Structure with estimates?

To turn fuzzy goals into a Work Breakdown Structure (WBS), decompose the objective into deliverable-oriented leaf tasks of 8 to 80 hours, then map dependencies and compute PERT-based effort estimates to create a coherent schedule.

What is the critical path method and how does it apply to project scheduling?

The critical path method identifies the longest sequence of dependent tasks in a project schedule, determining the shortest possible completion time. Mapping inter-task dependencies highlights this critical path to prioritize milestone tracking.

How do I create a project plan with a risk register for a feature roadmap?

Generate a project plan for feature roadmaps by decomposing goals into a WBS with milestones and dependencies, then filling a project plan template that includes a risk register to support governance and review.

Can I use PERT estimation for software migration planning?

PERT estimation applies to software migration planning by computing defensible effort estimates for WBS leaf tasks, ensuring accurate scheduling and dependency mapping for complex, time-bound initiatives.

What is the 8/80 rule in Work Breakdown Structure decomposition?

The 8/80 rule in WBS decomposition requires that leaf tasks take between 8 and 80 hours to complete, ensuring granular tracking and accurate effort estimation without excessive micro-management.

When should I not use WBS decomposition for project planning?

WBS decomposition may not suit projects lacking clear deliverables or strictly time-bound milestones, as it relies on structuring fuzzy goals into concrete, estimable leaf tasks to compute schedules and critical paths.