Estimation Flow

<!-- xid: FB65EC653F0F -->
<a id="xid-FB65EC653F0F"></a>

# Skill: estimation_flow

## Purpose

Execute the sequence `CAP-SUP-001 -> CAP-SUP-002 -> CAP-EST-001 -> CAP-EST-002` and prepare inputs for requirements work.

## Required Capability Definitions (XID)


## Inputs

- request
- change target list
- supplier definitions
- optional budget definition

## Outputs

- four-condition comparison result
- issue list
- cost estimate patterns
- solution options with effort and risk
- assumption list
- ambiguity classification result
- confirmation-required item list

## Startup

- Confirm the request and change target list exist.
- Confirm supplier definitions are available.
- Confirm budget definitions exist when cost estimation is required.
- Record `unknown` for missing evidence before proceeding.

## Planning

- Define the estimation scope and target assumptions.
- Map each business activity to its supporting capability:
  - supplier four-condition check -> `CAP-SUP-001`
  - cost estimation -> `CAP-SUP-002`
  - solution option generation -> `CAP-EST-001`
  - assumption ambiguity classification -> `CAP-EST-002`
- Define the step order: `CAP-SUP-001 -> CAP-SUP-002 -> CAP-EST-001 -> CAP-EST-002`.
- Prepare management rows for supplier checks, cost patterns, options, and assumptions.

## Execution

- Perform supplier four-condition check by executing `CAP-SUP-001`.
- Perform cost estimation by executing `CAP-SUP-002`.
- Perform solution option generation by executing `CAP-EST-001`.
- Consult on option differences, direction tradeoffs, and assumption impacts when comparison cannot be closed inside the current boundary.
- Perform assumption ambiguity classification by executing `CAP-EST-002`.

## Monitoring and Control

- Check that each required supplier and assumption item has a recorded result.
- Downgrade weakly supported assumptions to `unknown`.
- Preserve explicit assumption gaps for confirmation.

## Closure

- Confirm all rows are finalized as `done`, `unknown`, or `out_of_scope`.
- Hand off assumptions that need confirmation.
- Escalate out-of-scope supplier or budget items when reassignment is required.

## Rules

- Do not approve supplier adoption.
- Do not approve final budget or delivery direction.
- Every unresolved assumption must remain explicit.

## Reporting Contract (共通報告)



- reporting_profile: phase_summary

Use the shared [Skill Reporting Contract](../../docs/core/contracts/081_skill_reporting_contract.md#xid-6B2D9F4A1C73) in the final report. Start with these headings in this order:

1. Status — done, partial, blocked, or escalated
2. Result — what was produced or decided
3. Evidence — output, evidence, checks, or XIDs
4. Open Items — unresolved unknowns, risks, judgments, or なし
5. Handoff — next owner and next action, or なし

Keep this summary-first section visible before Skill-specific detail; do not omit empty sections.