budget

To track project budget burn against phase caps, this Skill allocates per-project token and dollar budgets, monitors consumption against per-phase limits, and records burn entries to metrics.tokens and metrics.cost to surface overruns for governance.

Allocating per-phase budgets across multiple projects is handled by defining per-project token and dollar caps, distributing sub-budgets to each phase, and using ADR-backed overrides when phase limits need adjustment during OKR derivation or project close.

Yes, you can use ADR-backed overrides to adjust budget allocations mid-project, allowing governance teams to modify per-phase sub-budgets while maintaining an auditable record of changes made to the original token and dollar caps.

Burn tracking integrates with budget-monitor and close-eval by logging token and cost consumption entries to metrics.tokens and metrics.cost, enabling downstream tools to generate overrun reports and Chief reports during project close.

You need per-project token and dollar budgets for OKR derivation when managing multiple projects that require strict cost-management controls, ensuring phase caps prevent misallocation and provide accurate financial governance.

Budget overrun reporting requires per-phase allocations because distributing sub-budgets across phases identifies exactly which stage causes overspending, preventing cascading overruns and enabling targeted ADR-backed overrides before the total project cap is exceeded.