Generate a Stage 2 Conceptual Budget — CSI-structured budget from actual plans, cross-checked against master exclusions/inclusions per discipline. Flags scope gaps proactively. Outputs HTML budget + Excel exclusions sheet.
How this skill is triggered — by the user, by Claude, or both
Slash command
/contractor-estimating:conceptual-budget [project description with plan set, or leave blank to start interactively][project description with plan set, or leave blank to start interactively]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a structured conceptual budget from an actual plan set (SD, DD, or CD). The bridge between ROM alignment and formal bidding — the client has plans, you have scope, you need a defensible budget that's been scope-checked against master discipline checklists.
Generate a structured conceptual budget from an actual plan set (SD, DD, or CD). The bridge between ROM alignment and formal bidding — the client has plans, you have scope, you need a defensible budget that's been scope-checked against master discipline checklists.
The canonical use case: "Scope the project per CSI division and discipline, check against cost books, and produce a structured budget broken out by division. Act as a scope checker — catch things like: 'Did you forget the emergency power because this is a hospital? You need a generator.'"
HTML + XLSX — always. DOCX is opt-in only.
Conceptual Budget HTML (primary) — Same structure as ROM but with:
@page { margin: 0 } print CSS blockSave as contractor_conceptual_budget_[project-slug]_[YYYY-MM].html.
Excel exclusions/inclusions workbook — Per-discipline, filtered to this project's divisions. A raw master list freaks people out — the output needs to be contextual to the project's divisions. Save as contractor_exclusions_[project-slug]_[YYYY-MM].xlsx.
DOCX (opt-in only) — Generate via contractor-docs only if the client explicitly requests an editable version. Save as contractor_conceptual_budget_[project-slug]_[YYYY-MM].docx.
Same as ROM, plus:
Invoke the estimating-workflow skill for Phases 1-5 with scope-check emphasis:
Skip Phases 6-8 (formal exclusions list, sub bid packages, formal proposal generation). Those come in /formal-bid.
For each applicable discipline, cross-reference against master checklists and call out gaps:
Process:
references/clarifications-master.md and references/exclusions-master.mdFlag categories:
references/rs-means-reference.md — Unit cost workflow with local market multiplierreferences/cost-reference.md — SF benchmarks for sanity checkreferences/fee-reference.md — A&E fee buildup if combined scopecontractor-brand examples folderStructure expanded from ROM:
File: contractor_conceptual_budget_[project-slug]_[YYYY-MM].html
Per-discipline filtered exclusions/inclusions as XLSX.
Workbook structure:
Generated via openpyxl. File: contractor_exclusions_[project-slug]_[YYYY-MM].xlsx.
At delivery, end with:
Conceptual Budget delivered with [N] scope-check findings flagged.
Review the findings, coordinate with the architect/engineer to close
any gaps, then run /formal-bid when you're ready to send packages
to subcontractors for pricing.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub sunrise-systems/contractor-toolkit --plugin contractor-estimating