plan-schedule

Plan tasks.yaml into capacity-constrained batches and milestone gates with YAML/MD artifacts.

1|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ezagent42/prd2impl --skill plan-schedule
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-schedule
Source: https://github.com/ezagent42/prd2impl/tree/main/skills/skill-4-plan-schedule
Command: npx skills add https://github.com/ezagent42/prd2impl --skill plan-schedule

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans and schedules multi-line projects by converting a tasks.yaml into time-boxed batches, milestone gates, and a visible timeline.

Core Features & Use Cases

  • Transform a task graph into executable batches aligned with team capacity and dependencies.
  • Define milestones with gates, generate execution artifacts, and support dev-loop handoff.
  • Use Case: for a project with 3 lines, plan daily batches and track progress across milestones.

Quick Start

Use this skill to generate an end-to-end execution plan from your current tasks.yaml, create batches and milestones, and produce the resulting YAML/Markdown artifacts.

Frequently Asked Questions about plan-schedule

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

FAQPage Schema
How do I schedule project tasks into execution batches and milestones?▼

To schedule tasks into execution batches and milestones, you can convert a tasks.yaml file into time-boxed batches aligned with team capacity and dependencies, generating structured YAML and Markdown artifacts for review.

Can I plan daily batches for multiple teams from a tasks.yaml file?▼

Yes, you can plan daily batches for multi-line teams from a tasks.yaml file. The process builds batches with capacity constraints and defines milestones with gate checks to coordinate team execution.

What is the best way to convert a task graph into a time-boxed execution plan?▼

The best way to convert a task graph into a time-boxed execution plan is to resolve the plans_dir path, build batches respecting capacity limits, and define milestones with gates, outputting YAML/MD artifacts.

Does this approach support milestone gate checks for multi-line team coordination?▼

Yes, milestone gate checks are supported for multi-line team coordination. The scheduling process defines milestones with specific gates and generates collaboration artifacts to support dev-loop handoff.

Do I need a tasks.yaml file to generate timeline and collaboration artifacts?▼

Yes, you need a tasks.yaml file to generate timeline and collaboration artifacts. An optional docs/plans/project.yaml can also be used to further structure the execution plan and timelines.

What outputs are generated when scheduling tasks into milestones and batches?▼

When scheduling tasks into milestones and batches, the outputs generated are structured YAML and Markdown artifacts. These files provide timelines, gate checks, and execution plans for review and handoff.