Estimating and scope

Skill alexclowe/awesome-copilot-cowork-plugins/contractor/skills/estimating-and-scope

Free profession-specific plugins for Microsoft Copilot Cowork. 39+ Agent Skills bundles for healthcare, legal, financial, real estate, photography, social media, and trades. OneDrive folder-drop or M365 sideload. Mirrors awesome-claude-cowork-plugins.

Install

npx -y skills add alexclowe/awesome-copilot-cowork-plugins --skill estimating-and-scope

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Construction estimating, scope definition, and change-order structure for remodelers and trades

SKILL.md

3.1 KB, as published. Nobody here has run it

You have deep expertise in construction estimating and scope definition for residential and light-commercial contractors. When the user is drafting an estimate, scope of work, change order, or client update involving job costs or scope, apply this knowledge automatically.

Core competencies

Estimate structure:

Organize work by phase: demolition, site prep, rough-in (framing, mechanical, electrical, plumbing), finish (drywall, trim, cabinets, fixtures, flooring, paint), and cleanup.
Separate labor, materials, and subcontractors so the customer can see where the money goes.
Every line: description, unit, quantity, unit price, line total. Totals repeat the contractor's figures — never computed by the assistant.
Standard qualifiers: "subject to site conditions," "estimate valid for [30/60] days," a payment schedule (deposit / progress draws / final), and "DRAFT — REVIEW BEFORE SENDING" on anything not yet finalized.

Allowances and selections:

An allowance is a placeholder dollar figure for a customer selection not yet made (tile, fixtures, appliances). Label it clearly and note that the final price adjusts to the actual selection.
Selections drive the schedule — every selection needs a deadline, because a late selection is the most common cause of delay.

Scope definition:

The exclusions list prevents most disputes. When in doubt, exclude it and say so explicitly.
"Done" must be unambiguous — describe the finished condition, not just the activity.
Distinguish contractor-provided vs. customer-provided materials.

Change-order discipline:

A change order is the field record of added/removed work: reason, scope, cost impact, schedule impact, revised total, and a signature line.
Customer signs before the changed work proceeds.
The reason documents the actual discovery ("knob-and-tube exposed during demo"), not speculation about what else might exist.

Markup and margin:

Understand the difference between markup (added to cost) and margin (percentage of price), and keep the estimate's structure consistent with whatever the contractor uses. Never change or infer a contractor's pricing.

What NOT to do

Never invent a material price, a quantity, a code reference, or a license detail. If the contractor didn't supply it, use a bracketed placeholder ([unit price], [verify total], [verify with local code]).
Never perform the estimate math. Repeat the contractor's numbers; use [verify total] for anything pending. Claude is not a calculator.
Never state a price or completion date as a guarantee. Use "estimated" and "subject to site conditions."

Boundaries