estimator

name: estimator description: >- Project estimation tool with interactive workflow. Breaks down projects into functional components, calculates cost ranges (optimistic/realistic/pessimistic) with auto-detected risk coefficients. Generates structured Markdown ready for propositor. Supports dev, refonte, TMA, and audit projects with 3 granularity levels. Use when user needs to estimate costs, calculate workload, prepare project budgets, or says "estime", "chiffrage", "JH", "combien coûterait". Not for invoicing, accounting, contract review, or projects without technical scope.

Estimator — Project Estimation Tool

Overview

Estimator transforms functional requirements into structured, argumented cost estimates through an interactive 4-phase workflow with mandatory checkpoints. Outputs client-ready Markdown documents consumable by Propositor.

Quick Decision Tree

┌─────────────────────────────────────────────────────────────────┐
│                    What type of estimation?                      │
└─────────────────────────────────────────────────────────────────┘
                            │
        ┌───────────────────┼───────────────────┐
        ▼                   ▼                   ▼
┌───────────────┐   ┌───────────────┐   ┌───────────────┐
│  NEW PROJECT  │   │  EVOLUTION    │   │  AUDIT/TMA    │
│  (dev/refonte)│   │  (features)   │   │  (review)     │
└───────┬───────┘   └───────┬───────┘   └───────┬───────┘
        │                   │                   │
        ▼                   ▼                   ▼
   Full workflow       Partial lots        Specific template
   (all 12 lots)       (impacted only)     (no recette for audit)

Main Workflow (4 Phases)

Phase 1: Qualification

Goal: Understand context and calibrate estimation

1. Analyze input (brief, brainstorm output, specs)
2. Ask clarification questions (≤3 if brief is clear)
3. Auto-detect: project type, granularity, coefficients

📍 Checkpoint 1: Present understanding + detected parameters for validation

→ See workflow-details.md for checkpoint format

Phase 2: Functional Breakdown

Goal: Identify ALL features (explicit AND implicit)

1. Extract features from brief
2. Identify implicit features (auth, logs, admin...)
3. Assign unique IDs (FCT-001, FCT-002...)
4. Prioritize: MVP / Should / Could
5. Provide AI suggestions

📍 Checkpoint 2: Present feature table + suggestions for validation

Phase 3: Task Evaluation

Goal: Estimate each task with ranges

1. Generate task tables per lot
2. Calculate: JH_Low × 0.8 | JH_Mid × coeff | JH_High × 1.3
3. Apply automatic recette (15% for dev, varies by type)

📍 Checkpoint 3: Present detailed estimation for validation

→ See lots-templates.md for lot structures

Phase 4: Valorization & Synthesis

Goal: Convert JH to budget, document assumptions

1. Apply TJM (default 450€)
2. Generate budget scenarios (Light/Low/Mid/High)
3. Document technical registry (assumptions, risks, stack choices)

📍 Final Checkpoint: Complete document ready for export or Propositor

Granularity Auto-Detection

Coefficient Auto-Detection

→ See coefficients.md for detailed formulas

Tech Stack Preferences

Commands Reference

During Session

Launch Flags

Output Format

Estimator produces structured Markdown with parseable tags:

<!-- ESTIMATOR_DATA_START -->
| Lot | JH Low | JH Mid | JH High |
|-----|--------|--------|---------|
...
<!-- ESTIMATOR_DATA_END -->

<!-- ESTIMATOR_BUDGET_START -->
| Scenario | JH | Amount HT |
|----------|-----|-----------|
...
<!-- ESTIMATOR_BUDGET_END -->

→ See output-format.md for complete template

Critical Rules

1. Mandatory checkpoints — No one-shot generation
2. Proactive AI suggestions — Implicit features, risks, alternatives
3. Ask when uncertain — Never guess, request clarification
4. FCT-xxx traceability — Each task references a feature
5. Complete technical registry — Document all assumptions
6. User's language — Output in input language
7. Parseable tags — For Propositor integration

Synergies

Inputs From

• brainstormer → Synthesis report, decisions
• code-promptor → Technical brief, constraints
• resumator → Meeting notes, requirements

Outputs To

• propositor → Primary — Full estimation for commercial proposal
• planificator (future) → JH per lot for detailed planning
• tracker (future) → Initial estimate as tracking reference

Limitations

This skill does NOT handle:

• Invoicing or accounting
• Contracts or legal aspects
• Estimates without technical scope
• Negotiation (see negociator)
• Detailed planning (see planificator)

Version History

Current: v1.0.0

Owner

• Author: Édouard
• Contact: Via Claude.ai