project-planner

Generate deterministic project plans with scope, milestones, WBS, dependencies, and critical path.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cromesdk/ai-skills --skill project-planner-cromesdk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-planner
Source: https://github.com/cromesdk/ai-skills/tree/main/skills/project/project-planner
Command: npx skills add https://github.com/cromesdk/ai-skills --skill project-planner-cromesdk

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill transforms vague project ideas or detailed requests into structured, actionable project plans, ensuring clarity on scope, timelines, and deliverables.

Core Features & Use Cases

  • Comprehensive Planning: Generates detailed project plans including scope, milestones, work breakdown structures (WBS), dependencies, critical path, estimates, risks, and acceptance criteria.
  • Use Case: When you need to outline the steps for developing a new software feature, from initial concept to deployment, this skill will provide a clear roadmap.

Quick Start

Use the project-planner skill to create a project plan for launching a new mobile app.

Frequently Asked Questions about project-planner

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

FAQPage Schema
How do I create an execution-ready project plan with scope definition and milestone planning?

A project plan covers scope definition, milestone planning, and work breakdown structure (WBS). It provides dependency mapping, critical path identification, effort estimation, risk planning, and acceptance criteria for execution-ready delivery.

How do I map dependencies and identify the critical path for a software delivery roadmap?

Dependency mapping and critical path identification are core project planning features. They sequence your work breakdown structure to determine the minimum delivery timeline and highlight schedule risks.

Can I generate a task breakdown and resourcing plan for a new software feature launch?

Yes, generating a task breakdown and resourcing plan for new software features is a primary use case. It transforms detailed requests into implementation roadmaps with effort estimates and tradeoff planning.

What is the best way to replan an implementation roadmap after scope changes?

The best way to replan after scope changes is to regenerate the deterministic project plan. This updates the work breakdown structure, dependency mapping, and timeline estimation to reflect new requirements.

Does this project planning approach include risk management and acceptance criteria?

Yes, comprehensive project planning includes risk management and acceptance criteria. It identifies potential schedule risks and defines clear deliverable conditions to ensure execution readiness.

When do I need a work breakdown structure for project estimation and tradeoff planning?

You need a work breakdown structure (WBS) when transforming vague ideas into actionable plans. It enables accurate effort estimation, dependency-aware scheduling, and tradeoff planning for delivery roadmaps.