estimate

Estimate costs and effort for architecture-driven projects using bottom-up, T-shirt, and three-point sizing.

2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Modular-Earth-LLC/solutions-architecture-agent --skill estimate-modular-earth-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimate
Source: https://github.com/Modular-Earth-LLC/solutions-architecture-agent/tree/main/skills/estimate
Command: npx skills add https://github.com/Modular-Earth-LLC/solutions-architecture-agent --skill estimate-modular-earth-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cost estimation and effort planning for architecture initiatives, enabling structured budgeting, risk-informed SOW pricing, and stakeholder alignment.

Core Features & Use Cases

  • Generate bottom-up and three-point cost estimates with LOE breakdowns.
  • Produce team composition plans and infrastructure cost models.
  • Use in budgeting, fundraising, or SOW pricing for enterprise engagements.

Quick Start

Provide an initial cost and effort estimate for the requested architecture under given constraints.

Frequently Asked Questions about estimate

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

FAQPage Schema
How do I generate a bottom-up cost estimate for an architecture-driven project?

Generate a bottom-up cost estimate by reading project requirements and architecture context, then calculating effort breakdowns and infrastructure costs. The process outputs a versioned estimate file with LOE details to inform SOW pricing and budgeting decisions.

What is the best way to calculate SOW pricing and effort for enterprise engagements?

Calculate SOW pricing by applying bottom-up, T-shirt, or three-point sizing to your architecture requirements. This produces team composition plans and infrastructure cost models, enabling risk-informed budgeting and stakeholder alignment for enterprise engagements.

Can I use three-point sizing for PoC proposal budgeting?

Yes, you can use three-point sizing for PoC proposal budgeting. The estimation process supports three-point sizing alongside bottom-up and T-shirt sizing, with optional depth controls to scale the calculation accuracy for PoC or enterprise contexts.

Do I need a requirements.json file to estimate project costs?

Yes, a requirements.json file is a required prerequisite. The estimation process reads context from knowledge_base prerequisites including requirements.json and architecture.json, while optionally using data_model.json, security_review.json, and integration_plan.json.

What outputs do I get when estimating LOE and infrastructure costs?

When estimating LOE and infrastructure costs, you get versioned results written to knowledge_base/estimate.json and knowledge_base/engagement.json. These outputs capture cost models, effort breakdowns, and team composition for budgeting and SOW pricing.