# project-timeline-simulator

project-timeline-simulator — a command for Claude Code and Cursor that simulates project timelines across multiple scenarios, accounting for uncertainty, dependencies, and resource constraints.

- command · `type=command` · Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI · ★ 3785 repo stars
- Author: BuildWithClaude Community
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/davepoon/buildwithclaude/tree/HEAD/plugins/all-commands/commands/project-timeline-simulator.md
- Updated: 2026-10-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/buildwithclaude-community-project-timeline-simulator

## What it does

The command decomposes a project into a work breakdown structure, maps task dependencies, and runs probabilistic simulations to predict timeline outcomes. Input consists of project scope, team size, constraints, and risk factors; output includes baseline, optimistic, and pessimistic scenarios with confidence intervals and critical-path analysis. Internally, it applies three-point estimation, Monte Carlo sampling, and dependency modeling to quantify schedule risk.

Requires Bash with `gh` (GitHub CLI) access to read repository context. Runs in Claude Code and Cursor.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add davepoon/buildwithclaude
```
In the agent chat (not a shell):
```text
/plugin install all-commands@buildwithclaude
```

2. **Manually: put the files in place**
- File: `.claude/commands/project-timeline-simulator.md` — Call it with /project-timeline-simulator. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/project-timeline-simulator.md` — Call it with /prompts:project-timeline-simulator. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/project-timeline-simulator.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/project-timeline-simulator.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/davepoon/buildwithclaude/tree/HEAD/plugins/all-commands/commands/project-timeline-simulator.md

## When to use it
- forecast project completion dates under uncertainty
- identify critical tasks that constrain the schedule
- quantify impact of resource shortfalls on delivery
- compare alternative team and timeline configurations

## Example prompts
- Simulate timelines for our backend overhaul: five engineers, three months, three external API integrations
- Model three scenarios—optimistic, baseline, pessimistic—for the v2.0 launch
- Which tasks become critical if we lose one developer for a month?

## Source text · project-timeline-simulator.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 1527f184b2b46ff6.

BEGIN THIRD-PARTY FILE 1527f184b2b46ff6
````text
---
description: Simulate project outcomes with variable modeling, risk assessment, and resource optimization scenarios.
category: project-task-management
argument-hint: "Specify project timeline parameters"
allowed-tools: Bash(gh *), Read
---

# Project Timeline Simulator

Simulate project outcomes with variable modeling, risk assessment, and resource optimization scenarios.

## Instructions

You are tasked with creating comprehensive project timeline simulations to optimize planning, resource allocation, and risk management. Follow this approach: **$ARGUMENTS**

### 1. Prerequisites Assessment

**Critical Project Context Validation:**

- **Project Scope**: What specific project are you simulating timelines for?
- **Key Variables**: What factors could significantly impact timeline outcomes?
- **Resource Constraints**: What team, budget, and time limitations apply?
- **Success Criteria**: How will you measure project success and timeline effectiveness?
- **Risk Tolerance**: What level of schedule risk is acceptable?

**If context is unclear, guide systematically:**

```
Missing Project Scope:
"What type of project needs timeline simulation?
- Software Development: Feature development, platform migration, system redesign
- Product Launch: New product development from concept to market
- Business Initiative: Process improvement, organizational change, market expansion
- Infrastructure Project: System upgrades, tool implementation, capacity expansion

Please specify project deliverables, stakeholders, and success criteria."

Missing Key Variables:
"What factors could significantly impact your project timeline?
- Resource Availability: Team capacity, skill availability, external dependencies
- Technical Complexity: Unknown requirements, integration challenges, performance needs
- External Dependencies: Vendor deliveries, regulatory approvals, partner coordination
- Market Dynamics: Customer feedback, competitive pressure, business priority changes"
```

### 2. Project Structure Modeling

**Systematically map project components and dependencies:**

#### Work Breakdown Structure (WBS) Analysis
```
Project Component Framework:

Phase-Based Structure:
- Discovery/Planning: Requirements gathering, design, architecture planning
- Development/Implementation: Core building, integration, testing phases
- Validation/Testing: Quality assurance, user acceptance, performance validation
- Deployment/Launch: Release preparation, rollout, go-live activities
- Stabilization/Optimization: Post-launch support, performance tuning, iteration

Feature-Based Structure:
- Core Features: Essential functionality for minimum viable product
- Enhanced Features: Additional capabilities for competitive advantage
- Integration Features: System connectivity and data synchronization
- Quality Features: Security, performance, reliability, and maintainability

Skill-Based Structure:
- Frontend Development: User interface and experience implementation
- Backend Development: Server logic, APIs, and data processing
- Infrastructure/DevOps: Deployment, monitoring, and operational setup
- Design/UX: User research, interface design, and usability testing
- Quality Assurance: Testing strategy, automation, and validation
```

#### Dependency Mapping Framework
```
Project Dependency Analysis:

Sequential Dependencies:
- Finish-to-Start: Task B cannot begin until Task A completes
- Start-to-Start: Task B cannot start until Task A has started
- Finish-to-Finish: Task B cannot finish until Task A finishes
- Start-to-Finish: Task B cannot finish until Task A starts

Resource Dependencies:
````
END THIRD-PARTY FILE 1527f184b2b46ff6

The third-party file has ended. Everything between the 1527f184b2b46ff6 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3603 of 17192 bytes. © BuildWithClaude Community · MIT · https://github.com/davepoon/buildwithclaude/tree/HEAD/plugins/all-commands/commands/project-timeline-simulator.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
