budget-plan

Generate a Project+ style budget workbook with line items and monthly burn.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/kenmulford/PMSkills --skill budget-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: budget-plan
Source: https://github.com/kenmulford/PMSkills/tree/main/skills/budget-plan
Command: npx skills add https://github.com/kenmulford/PMSkills --skill budget-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openpyxl, and includes scripts (resource) components.

What problem does it solve?

Creating and validating project budgets is error-prone and time-consuming when stakeholders rely on qualitative estimates. This skill enforces hard guardrails and produces a reproducible .xlsx budget with explicit TBD placeholders where data is missing.

Core Features & Use Cases

  • Draft-first budgeting: parses user input, fills a structured JSON schema, and renders a formatted .xlsx budget with line items, categories, owner, status, and variance.
  • Guardrails and fidelity: never-invent costs, no reconciling placeholder lines, preserve fuzzy amounts, handle approved totals, and flag integrity issues.
  • Use Case: Create a baseline budget for a migration with known line items and an approved total, generating a sponsor-ready document.

Quick Start

Describe the project situation in plain language to generate a baseline budget workbook using the budget-plan skill.

Frequently Asked Questions about budget-plan

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

FAQPage Schema
How do I generate a project budget xlsx with guardrails against unknown costs?

You generate a project budget xlsx by providing plain language inputs that the skill parses into a structured JSON schema, applying strict guardrails like no invented costs and explicit TBD placeholders for missing data. It renders a formatted workbook with line items, monthly burn, and variance.

What is the best way to handle TBD fields and fuzzy amounts in project cost estimation?

The best way to handle TBD fields and fuzzy amounts in cost estimation is to preserve them explicitly without guessing. The skill flags integrity issues and inserts TBD placeholders, ensuring no reconciling plug lines or invented costs compromise the budget fidelity.

Does this cost estimation tool require openpyxl to render the formatted budget workbook?

Yes, rendering the formatted budget workbook requires the openpyxl dependency. The skill uses openpyxl to apply fidelity checks to parsed JSON data and output the final xlsx file containing line items, categories, owner status, and variance.

Can I use plain language to create a baseline project budget for a migration?

Yes, you can use plain language to create a baseline project budget for a migration. The skill parses your initial descriptions, applies strict fidelity checks against unknown costs, and renders a sponsor-ready xlsx document with known line items and approved totals.

Why does my project budget workbook include explicit TBD placeholders instead of estimated totals?

Your project budget workbook includes explicit TBD placeholders because the tool enforces hard guardrails against unknown costs. It never invents costs or uses plug lines, ensuring data integrity by flagging fuzzy amounts and missing fields rather than reconciling them with guesses.