estimate-snapshot

Generate immutable estimate snapshots with provenance and QA summaries.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sgttomas/chirality-piping --skill estimate-snapshot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimate-snapshot
Source: https://github.com/sgttomas/chirality-piping/tree/main/skills/estimate-snapshot
Command: npx skills add https://github.com/sgttomas/chirality-piping --skill estimate-snapshot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the generation of immutable, provenance-first estimate snapshots for bounded sets of deliverables and packages, enabling audit-friendly budgeting and decision-making.

Core Features & Use Cases

  • Generates per-scope WBS/CBS rollups and QA-ready summaries for straightforward review.
  • Writes results to a quarantined tool root under a timestamped folder to preserve provenance and traceability.
  • Enforces a validated BASIS_OF_ESTIMATE and local PRICE_SOURCES to eliminate reliance on external pricing.
  • Delivers deterministic outputs that can be re-run with identical inputs for audits.

Quick Start

Provide a scope and BASIS_OF_ESTIMATE, then run the tool to create a new timestamped snapshot under the estimates root.

Frequently Asked Questions about estimate-snapshot

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

FAQPage Schema
How do I create immutable estimate snapshots for budgeting deliverables?

To create immutable estimate snapshots for budgeting, you provide a bounded scope and a validated BASIS_OF_ESTIMATE to generate timestamped, provenance-backed outputs. The tool writes results to a quarantined folder to preserve traceability for audits.

What is provenance-first cost modeling and when do I need it?

Provenance-first cost modeling tracks the exact source and validation of every pricing input within your estimates. You need it for audit-friendly budgeting when deterministic, reproducible outputs are required for financial review.

How do I generate WBS rollups and QA summaries for bounded packages?

You generate WBS and CBS rollups by running the tool against your defined deliverable scopes. It automatically produces QA-ready summaries and rollups using local PRICE_SOURCES to eliminate reliance on external pricing.

Can I use local price sources instead of external pricing for cost estimates?

Yes, you can and must use local PRICE_SOURCES for cost estimates. The tool enforces a validated BASIS_OF_ESTIMATE and local pricing inputs to ensure deterministic outputs that can be re-run identically for audits.

What is the best way to ensure audit-friendly traceability for project estimates?

The best way to ensure audit-friendly traceability is to generate immutable snapshots under a timestamped tool root. This approach enforces provenance requirements and write boundaries, creating deterministic outputs for straightforward review.

Why do my estimates need a validated basis of estimate before generating snapshots?

Estimates need a validated BASIS_OF_ESTIMATE to enforce provenance and eliminate untracked pricing inputs. This constraint ensures that generated snapshots are deterministic, reproducible, and satisfy QA reporting requirements for bounded deliverables.