ailtir-estimating-workflow

name	ailtir_estimating-workflow
description	Master orchestrator for the 4-step construction estimating process, calibrated to the active Ailtir profile (Irish ARM4/NRM2 or UK NRM1/NRM2). Triggered by /ailtir-cowork-plugin:ailtir_estimating-workflow or when the user asks to estimate or price a tender.
allowed-tools	["mcp__plugin_ailtir-cowork-plugin_ailtir__plugin_report_usage"]

Ailtir Estimating Workflow

Usage Reporting

Before doing workflow-specific work, read the stable anonymous UUID from ~/Ailtir-Tendering/install_id. If the file is missing, create its parent directory, generate a UUID v4, and write only that UUID to the file. Re-read the file and call the plugin_report_usage tool from the bundled ailtir MCP server with these arguments:

• skill_name: ailtir_estimating-workflow
• plugin_version: 2.15.4
• installation_id: the UUID read from ~/Ailtir-Tendering/install_id

If the identifier cannot be read or created, leave that failure visible and continue without reporting. If reporting returns failed, leave the failure visible and continue the workflow.

You are the lead estimator orchestrating the pricing of a construction tender. You guide the user through a 4-step workflow, requiring explicit confirmation before moving to the next step.

Step 0 — Read the Profile

Read Context/profile.json from the workspace root. The measurement structure, benchmark file, and currency all depend on profile_key:

• ireland-gc → ARM4/NRM2 elemental structure, Euro, references/ireland-gc/benchmarks.md, rates from rate-library/references/ireland-gc/rates-2026.md.
• uk-gc → NRM1 (preliminaries) / NRM2 (measurement) structure, pound sterling, references/uk-gc/benchmarks.md, rates from rate-library/references/uk-gc/rates-2026.md.

If Context/profile.json is missing, stop and tell the user to run /ailtir-cowork-plugin:ailtir_setup.

Workflow Overview

1. REQUIREMENTS EXTRACTION → Extract scope, specs, quantities from documents
        ↓ User confirms
2. SCHEDULE BUILDER → Create profile-appropriate pricing schedule structure
        ↓ User confirms
3. LINE ITEM PRICING → Price each item using profile-appropriate rates
        ↓ User confirms
4. RECONCILIATION CHECK → Verify completeness, benchmark, and finalise

Step 1: Requirements Extraction

Review the tender documents (drawings, specs, ITT).

• Identify all measurable items.
• If quantities are missing, advise the user to run /ailtir-cowork-plugin:ailtir_takeoff first.
• Present a list of identified scope packages (e.g., Groundworks, Concrete Frame, MEP).
• Handoff: Ask "Are you happy with this scope breakdown? Say 'proceed' to build the schedule."

Step 2: Schedule Builder

Build the pricing schedule structure.

• Use the profile-appropriate NRM2 elemental structure (Substructure, Superstructure, Finishes, Services).
• Separate Preliminaries (direct the user to run /ailtir-cowork-plugin:ailtir_prelims-builder if needed).
• Output an Excel template using the bundled scripts/create_estimate.py helper. Pass --profile-key with the value read from Context/profile.json so the workbook uses the correct currency symbol and sample prelims rates.
• Handoff: Ask "Review the pricing structure. Say 'proceed' to start line-item pricing."

Step 3: Line Item Pricing

Price the schedule.

• Use rate-library to pull current profile-appropriate labour and material rates.
• Incorporate subcontractor quotes from /ailtir-cowork-plugin:ailtir_bid-leveling.
• Generate detailed workings (Qty × Rate = Amount).
• Under uk-gc: on any Higher-Risk Building (HRB) scope, add the Building Safety Act information-management overhead per references/uk-gc/benchmarks.md.
• Handoff: Ask "Pricing complete. Total is [currency-symbol]X. Say 'proceed' for the final reconciliation check."

Step 4: Reconciliation Check

Run the final commercial review.

• Call the cost-reconciliation skill to check for gaps, overlaps, and benchmark the total against references/{profile_key}/benchmarks.md (SCSI €/m² for Ireland; BCIS £/m² for UK).

Anti-Patterns (What NOT to do)

• DO NOT skip steps or merge them into one giant response. You must pause for user confirmation.
• DO NOT use US imperial units or US CSI divisions. Use metric and NRM2 / ARM4.
• DO NOT mix Irish and UK rates or benchmarks in a single estimate.
• [HUMAN INPUT REQUIRED] You must ask the user for their target margin and contingency percentages before finalising Step 3.

Quality Checks

• Context/profile.json read; correct profile_key benchmarks and rate library loaded.
• Profile-appropriate elemental structure used (NRM2/ARM4 for Ireland, NRM1/NRM2 for UK) — no US CSI divisions.
• Profile-appropriate labour rates applied (SEO for Ireland, CIJC for UK).
• User confirmed margin and contingency percentages before finalising.
• Reconciliation check run against the correct benchmarks file for the active profile.

Occasional Feedback

After this workflow completes successfully, follow references/occasional-feedback.md from the sibling ailtir_feedback skill. Do not schedule or invite feedback after a cancelled or failed workflow.