Update to Rohas Legal AI: Practice

{
  "description": "Build transparent, stage-based legal cost estimates and budgets with staffing, rates, hours, assumptions, exclusions, disbursements, taxes, scenarios, contingencies, and change controls. Use for engagement, matter planning, litigation budgets, fixed or capped fees, tenders, or estimate updates.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 303
    }
  ],
  "name": "costing-estimator",
  "skill_md_contents": "---\nname: costing-estimator\ndescription: >-\n  Build transparent, stage-based legal cost estimates and budgets with staffing,\n  rates, hours, assumptions, exclusions, disbursements, taxes, scenarios,\n  contingencies, and change controls. Use for engagement, matter planning,\n  litigation budgets, fixed or capped fees, tenders, or estimate updates.\n---\n\n# Costing Estimator\n\nMake the estimate reproducible and useful for decisions. Distinguish a forecast,\nrange, cap, fixed fee, retainer, contingency, and statutory or recoverable cost.\n\n## Intake\n\nObtain the scope and deliverables, jurisdiction, matter stage, timetable,\ncomplexity drivers, documents and data volume, parties, forums, staffing model,\nrates and currency, fee arrangement, assumptions, exclusions, disbursements,\nexperts and counsel, taxes, billing guidelines, recoverability, risk tolerance,\nprior actuals, and client reporting requirements.\n\n## Estimation method\n\n1. Define the priced scope, start and end point, work breakdown, deliverables,\n   dependency on client or third parties, and excluded work.\n2. Break work into stages and tasks with role, rate, hours or units, quantity,\n   frequency, and calculation basis.\n3. Separate professional fees, expenses, court or registry fees, experts,\n   counsel, vendors, travel, taxes, currency effects, and client internal costs.\n4. State assumptions about pleadings, hearings, negotiations, data volume,\n   witnesses, counterparties, revisions, urgency, cooperation, and outcome.\n5. Build low, expected, and high scenarios around identifiable drivers rather\n   than applying an unexplained percentage.\n6. Address discounts, blended rates, caps, collars, fixed fees, success elements,\n   retainers, replenishment, write-offs, and what happens when scope changes.\n7. Compare forecast with actuals and estimate-to-complete when updating a live\n   matter. Explain variance by scope, rate, volume, timing, or efficiency.\n8. Identify client approvals, spending thresholds, notice triggers, contingency,\n   refresh cadence, and owner for each change.\n9. Explain whether taxes and disbursements are included, whether third-party\n   figures are quotes or estimates, and whether any amount may be recoverable.\n10. Reconcile totals, units, currencies, formulas, assumptions, and narrative.\n\n## Output\n\nProvide the stage budget, staffing and rate table, scenario comparison,\nassumptions and exclusions, disbursement schedule, cash-flow view, change-control\ntriggers, and update template.\n\n## Guardrails\n\nDo not present an estimate as a guarantee, omit foreseeable external cost, hide\nscope assumptions, double count, or imply recoverability. Do not use unlawful or\nunreasonable fee structures. Obtain approval under current engagement,\nprofessional, tax, procurement, and client-money rules.\n"
}