Skip to content
Skills Library
Management & product · Planning

program-planning

/program-planning

Creates program plans with timelines, milestones, dependencies, and critical path analysis. Use when starting a new program or replanning an existing one.

Repository
konductor ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Creates program plans with timelines, milestones, dependencies, and critical path analysis. Use when starting a new program or replanning an existing one.

Original author description

Creates program plans with timelines, milestones, dependencies, and critical path analysis. Use when starting a new program or replanning an existing one.

How it works

  1. Core Concepts
  2. Output Format
  3. Quality Gate
Original SKILL.md headings · 56 lines, 416 words
SKILL.md preview
---
name: program-planning
description: Creates program plans with timelines, milestones, dependencies, and critical path analysis. Use when starting a new program or replanning an existing one.
version: 1.0.0
tags: [skill, tpm, planning, timeline, milestones, dependencies]
---

# Program Planning

## Core Concepts

### Milestone Definition

Each milestone has: name, target date, exit criteria (measurable), owning team, and dependencies. Milestones mark phase transitions — not individual task completion. Use SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound).

### Dependency Mapping

Classify dependencies as: internal (within program), cross-team (other teams), external (vendors/partners). Each dependency has: source milestone, target milestone, type (finish-to-start, start-to-start), lead/lag time, and risk level if delayed.

### Critical Path

The longest sequence of dependent milestones determining minimum program duration. Identify float (slack) for non-critical milestones. Flag milestones with zero float as critical path items.

### Timeline Estimation

Convert T-shirt sizes to calendar ranges: XS (1-2d), S (3-5d), M (1-2w), L (3-4w), XL (5-8w). Apply buffer: 20% for well-understood work (the floor, applied to all work — there is no zero-buffer tier), 40% for novel, complex, unfamiliar, or otherwise uncertain work — the same estimation-uncertainty buffer the plan SOP's Step 5 (Estimate Timeline) applies ahead of its agentic-conversion projection. Account for holidays, on-call rotations, and team availability.

## Output Format

Generate a program plan with these sections:

1. **Program Summary** — name, objective, sponsor, TPM, start/end dates, team size
2. **Milestones Table** — columns: ID, Milestone, Owner, Target Date, Exit Criteria, Dependencies, Status
3. **Gantt-Style Timeline** — ASCII table showing milestones across weeks/months with `[====]` bars and `|` for dependencies
4. **Critical Path** — ordered list of critical path milestones with zero-float callout
5. **Dependency Map** — table: Source → Target, Type, Lag, Risk Level
6. **Resource Allocation** — team/person → workstream mapping with utilization %
7. **Risks to Plan** — top 3 schedule risks with mitigation (link to risk-management skill for full RAID)
8. **Task Management Integration** — task breakdown ready for import: task title, assignee, sprint, story points

## Quality Gate

**CRITICAL (must fix):**

- Milestones without measurable exit criteria
- Circular dependencies in the dependency map
- Critical path not identified or incorrect
- End date earlier than critical path minimum duration

**IMPORTANT (should fix):**

- No buffer applied to estimates (see Timeline Estimation above; the plan SOP's Step 5 carries the equivalent buffer, kept independent of its agentic projection)
- Dependencies missing risk assessment
- Resource over-allocation (>100% utilization)

**SUGGESTION:**

- Could add confidence levels per milestone (High/Medium/Low)
- Could identify parallel workstreams to compress timeline

Present findings as: CRITICAL → IMPORTANT → SUGGESTION. Ask: "Fix these issues? [y/n]" — unless `scope_confirmed` is true, in which case report all the findings and leave fixing to the caller, without asking.

Versions

The database has no other skills named program-planning.

Database snapshot: 13.11.2026 · package version 56d05f1fd8b2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100planning-mode
    Use this skill when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.
  • 100gantt-planner
    Generate interactive HTML Gantt charts with Critical Path Method (CPM) analysis from task lists and dependencies, highlighting the critical path and calculating float times. Use when the user asks to create a Gantt chart, schedule project tasks, analyze the critical path,…
  • 90integrated-roadmap
    Integrates every AI programme workstream plan - adoption, Champions, learning, knowledge, platform, agent delivery, governance and value - into one dated delivery plan with milestones, a critical path, cross-workstream dependencies and a baseline that changes only by decision.…
  • 90success-planning-framework
    Use to structure collaborative success plans with milestones, KPIs, and governance.
  • 90implementation-roadmaps
    Create or improve a phased product or engineering roadmap with milestones and dependencies. Use when organizing a larger initiative, sequencing releases, or turning a strategy into trackable work.
  • 100timeline-planning
    Use when asked for a project timeline, schedule, sprint plan, or Gantt chart, or after breaking work into issues - converts issue estimates and dependencies into a Mermaid Gantt chart with phases, milestones, and critical path

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.