Agent skill

thrivve-mc-when

Thrivve Partners Monte Carlo simulation to forecast completion date based on remaining work and historical throughput. Use when the user asks "when will I complete [N] stories/tasks" with historical daily throughput data. Requires at least 10 days of throughput history, a count of remaining items, and optional confidence level (default 85%).

Stars 0
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/blujaxfan/claude_skill_monte_carlo_flow/tree/main/thrivve-mc-when

SKILL.md

Thrivve Partners Monte Carlo 'When' Forecasting

Forecast when a specific number of stories or tasks will be completed using Monte Carlo simulation based on historical throughput data.

When to Use

Use this skill when the user provides:

  1. Historical throughput data (daily counts for at least 10 days)
  2. Number of stories/tasks remaining to complete
  3. A desired confidence level (optional, defaults to 85%)
  4. A start date (optional, defaults to today)

Common trigger patterns:

  • "In the last X days, the throughput has been [counts] - when will I complete [N] stories with [confidence]% confidence?"
  • "Based on throughput of [counts], when will we finish [N] stories if we start [date / 'today']?"
  • "Run Monte Carlo simulation for [counts] to complete [N] stories"
  • "I have [N] stories left, when will I be done?"

Quick Start

Execute the Monte Carlo simulation script:

bash
python scripts/thrivve-mc-when.py "<comma-separated-throughput>" <stories-remaining> <confidence-level> "<start-date>"

Example:

bash
python scripts/thrivve-mc-when.py "3,5,4,2,6,4,5,3,7,4,5,6,3,4,5" 100 85 "2025-10-27"

Input Requirements

  1. Throughput data: Minimum 10 days of daily completion counts

    • Format: Comma-separated integers (e.g., "3,5,4,2,6,4,5,3,7,4")
    • More data = better predictions (15-30 days recommended)
  2. Stories remaining: Integer count of items to complete

    • Must be greater than 0
    • Typical range: 10-500 (larger numbers may take longer)
  3. Confidence level: Percentage between 0-99 (default: 85)

    • 25%: Optimistic outcome (earlier date, lower certainty)
    • 50%: Median outcome (equal chance of earlier or later)
    • 70%: Balanced outcome
    • 85%: Conservative (commonly used in agile forecasting)
    • 95%: Very conservative (high certainty, later date)
    • 99%: Maximum practical confidence (extremely conservative)
    • Note: 100% confidence is not possible in probabilistic forecasting
  4. Start date: A date in any common format (default: today)

    • Supported formats: YYYY-MM-DD, DD/MM/YYYY, MM/DD/YYYY, "Month DD, YYYY", etc.

Output Format

The script provides:

  • Primary answer: Completion date at specified confidence level
  • Percentile forecasts: P25, P50, P70, P85, P95, P99 (dates)
  • Statistical summary: Mean, min, max dates across all simulations
  • Days analysis: Days required at different confidence levels
  • Throughput analysis: Statistics about historical data
  • JSON output: Structured data for further processing

Workflow

  1. Parse user's throughput data from their message
  2. Extract stories remaining and confidence level
  3. Run the Monte Carlo script with parsed parameters
  4. Present results in clear, actionable format
  5. Explain what the confidence level means in context

Interpreting Results

  • At X% confidence: "There's an X% chance you'll be done ON OR BEFORE this date" (uses the percentile: X)
  • P50 (median): Half of simulations finished earlier, half later
  • P85: 85% of simulations finished on or before this date
  • P95: 95% of simulations finished on or before this date
  • Range: Shows fastest and slowest completion from all simulations

Example: At 85% confidence, you'll complete the work on or before December 15th (P85), meaning there's an 85% chance of finishing on or before that date (and only a 15% chance it will take longer).

Advanced Usage

Optional parameters:

  • num_simulations: Number of Monte Carlo runs (default: 10,000)
    • Higher values increase accuracy but take longer
    • 10,000 is typically sufficient for reliable results

Methodology

For detailed explanation of Monte Carlo simulation methodology, assumptions, and limitations, see references/methodology.md.

Key points:

  • Uses random sampling from historical throughput
  • Runs thousands of simulations to build probability distribution
  • Assumes past patterns continue into the future
  • Does not account for trends or changing conditions

Example Interaction

User: "In the last 15 days, the throughput has been 3,5,4,2,6,4,5,3,7,4,5,6,3,4,5 - when will I complete 100 stories with 85% confidence, if I start today?"

Response steps:

  1. Parse throughput: [3,5,4,2,6,4,5,3,7,4,5,6,3,4,5]
  2. Parse stories remaining: 100
  3. Parse confidence: 85%
  4. Parse start date: today (2025-10-27)
  5. Run simulation
  6. Present results: "Given your start date of today (October 27, 2025), at 85% confidence you will complete 100 stories on or before November 19, 2025 (there's only a 15% chance it will take longer)"
  7. Provide percentile context and explain the forecast

Expand your agent's capabilities with these related and highly-rated skills.

blujaxfan/claude_skill_monte_carlo_flow

thrivve-mc-how-many

Thrivve Partners Monte Carlo simulation to forecast story/task completion based on historical throughput. Use when the user asks "how many stories/tasks will be completed by [date]" with historical daily throughput data. Requires at least 10 days of throughput history and a future target date. Provides probabilistic forecasts at specified confidence levels (default 85%).

0 0
Explore
mattpocock/skills

git-guardrails-claude-code

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

111,310 9,758
Explore
mattpocock/skills

handoff

Compact the current conversation into a handoff document for another agent to pick up.

111,310 9,758
Explore
mattpocock/skills

edit-article

Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.

111,310 9,758
Explore
mattpocock/skills

scaffold-exercises

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

111,310 9,758
Explore
mattpocock/skills

setup-pre-commit

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

111,310 9,758
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results