contractor-estimating

Use this agent when a construction estimate has been built or is nearing completion and needs to be reviewed before it goes to a client. Triggers proactively after Phase 5 (hard cost estimation) or Phase 8 (document generation), and explicitly when the user asks to review, check, or validate an estimate. <example> Context: User has finished building an estimate and wants it checked before sending. user: "Review my estimate before I send it to the client." assistant: "I'll use the estimate-reviewer agent to check this against our standards." </example> <example> Context: User has just completed Phase 5 pricing and wants to proceed to document generation. user: "Pricing looks good, let's move to document generation." assistant: "Before we generate the documents, let me use the estimate-reviewer agent to do a quick QA pass." </example> <example> Context: User shares an estimate file or summary and asks if it looks right. user: "Does this estimate look complete to you?" assistant: "I'll use the estimate-reviewer agent to go through it systematically." </example> <example> Context: User is about to present numbers to a client and wants a sanity check. user: "We're presenting this tomorrow — anything I should double-check?" assistant: "Let me run the estimate-reviewer agent to flag anything that could cause problems." </example>

Use this agent when writing scope of work narratives for a construction estimate, during Phase 2 of the estimating pipeline, or when a user asks to draft, write, or improve scope language for a construction project. This agent produces project-specific written scopes organized by CSI division — not boilerplate. <example> Context: User has completed Phase 1 (division applicability matrix) and needs written scope before pricing can start. user: "Let's write the scope for this project." assistant: "I'll use the scope-writer agent to draft the written scope by division." <commentary> Standard Phase 2 trigger — scope-writer produces the division-by-division scope narrative. </commentary> </example> <example> Context: User has a project description and wants scope language ready to send to a client or sub. user: "Write me a scope of work for a 3,500 SF restaurant TI." assistant: "I'll use the scope-writer agent to build out that scope." </example> <example> Context: User wants to improve or tighten existing scope language. user: "This scope feels too generic — can you make it more specific to the project?" assistant: "I'll use the scope-writer agent to rewrite this with project-specific detail." </example> <example> Context: User has a scope of work that needs to be reorganized by CSI division. user: "Can you organize this scope by CSI division?" assistant: "I'll use the scope-writer agent to restructure this into CSI format." </example>

Use this agent when generating subcontractor bid invitation packages for a construction project, during Phase 7 of the estimating pipeline, or when the user asks to create, prepare, or assemble bid packages for trades. This agent produces self-contained bid invitations per trade — ready to distribute. <example> Context: User has completed Phase 6 (exclusions/inclusions) and is ready to package bids for subs. user: "Let's put together the sub bid packages." assistant: "I'll use the sub-packager agent to build the bid invitations for each trade." </example> <example> Context: User has a finalized estimate and needs to go out to market for sub pricing. user: "We need to send this out to HVAC, plumbing, and electrical subs. Can you put together the packages?" assistant: "I'll use the sub-packager agent to create bid invitations for those three trades." </example> <example> Context: User wants to send the project to a single sub and needs a clean package. user: "Put together a bid package for our drywall sub." assistant: "I'll use the sub-packager agent to build that bid invitation." </example> <example> Context: User wants to update or regenerate bid packages after estimate revisions. user: "The HVAC scope changed — can you update that bid package?" assistant: "I'll use the sub-packager agent to regenerate the HVAC bid invitation with the updated scope." </example>

Compare and normalize returned subcontractor bids per trade — scope gaps, plug comparison, apples-to-apples adjustments, and an award recommendation. Use when sub bids come back after /sub-bid-package or /formal-bid. Triggers on "level these bids", "compare sub bids", "bid leveling", or "/bid-leveling".

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.

Generate a curated AIA A201-based construction contract from an accepted estimate. Fills in project-specific blanks, attaches scope + exclusions as exhibits, adds standard payment/insurance terms, and applies project-type riders. Outputs a signable DOCX.

Start the preconstruction pipeline end-to-end. Routes to the appropriate stage command (/rom, /conceptual-budget, /formal-bid) based on project readiness. Runs all 3 stages and 8 internal phases. Outputs HTML ROM + DOCX budget + formal bid DOCX + sub bid packages + optional AIA contract.

Eight-phase preconstruction estimating pipeline for general contractors. Division scoping, written scope, quantity takeoff, hard cost pricing, exclusions, sub bid packages, and branded document output. Triggered by /estimate, /rom, /conceptual-budget, /formal-bid.