estimate-prep

Generate estimation input packages with pricing libraries, LOE data, and BOE scaffolds.

Updated Aug 23, 2026

Search Tags:#workflow #planning #scaffold #estimation #two-phase #boe

Ready to run

npx skills add https://github.com/sgttomas/chirality-piping --skill estimate-prep

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: estimate-prep
Source: https://github.com/sgttomas/chirality-piping/tree/main/skills/estimate-prep
Command: npx skills add https://github.com/sgttomas/chirality-piping --skill estimate-prep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates the creation of complete estimation inputs for ESTIMATING workflows, including pricing libraries, LOE data, and project parameters, to enable accurate, consistent BOE generation with auditable provenance.

Core Features & Use Cases

Generate parametric pricing baselines and a BOE scaffold for human review.
Produce standardized input artifacts (PriceSources/INDEX.md, LOE matrices, and parameter files) to feed downstream estimation workflows.
Use Case: An estimator runs SCAFFOLD to assemble a full input package for a municipal project, then re-invokes with BOE to finalize BASIS_OF_ESTIMATE.md after approval.

Quick Start

Run the skill with PHASE=SCAFFOLD and supply DECOMPOSITION_PATH, SOURCE_DOCUMENTS, and PROJECT_CONTEXT; after human review, re-run with PHASE=BOE using SCAFFOLD_PATH and dependencies.

Frequently Asked Questions about estimate-prep

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

FAQPage Schema

How do I generate a BASIS_OF_ESTIMATE document from project parameters?▼

A two-phase estimation workflow generates a BASIS_OF_ESTIMATE document by first assembling input parameters, pricing libraries, and LOE data in a scaffold phase, then finalizing the document after human review. This approach enforces phase separation and ensures auditable provenance for the final estimate.

What is two-phase estimation and when do I need a scaffold output?▼

Two-phase estimation separates input assembly from final document generation, requiring a scaffold output when projects demand human-gated review of pricing baselines, LOE matrices, and project parameters before finalizing the complete estimation package for downstream workflows.

How do I prepare estimation inputs for a parametric pricing baseline?▼

Preparing estimation inputs involves supplying a decomposition path, source documents, and project context to generate standardized artifacts. This produces an input package containing a PriceSources index, LOE data, and parameter files that establish a consistent, auditable pricing baseline for downstream estimation workflows.

Can I use this estimation workflow for municipal project BOE generation?▼

Yes, this estimation workflow supports municipal project BOE generation by allowing estimators to assemble a full input package including pricing libraries and project parameters during the scaffold phase, then finalizing the BASIS_OF_ESTIMATE document after human review and approval.

What are the limitations of a human-gated estimation workflow?▼

A human-gated estimation workflow requires an explicit manual review and approval step between the scaffold and BOE phases, meaning it cannot autonomously generate final estimates without user intervention. It also enforces strict phase separation, preventing simultaneous generation of scaffolds and final BOE documents.