Daily Action Brief

Bundled guidance · v1.0.0 · synthetic sandbox. Evidence uploads cannot install or modify skills.

Open local report · Choose this skill

Inputs and workflow

# Daily Action Brief

Use decision_brief to summarize the current recorded snapshot, pending action states, protected obligations and bounded response options. Use calendar, collections, account_funding, data_freshness or missing_facts for a focused follow-up. Choose one supported task per translation; do not claim a chain has run.

The ledger's as-of date controls the report. A request for today does not authorize advancing the business date, fabricating new observations or silently closing a day. Clarify an explicit ISO date for any date-dependent follow-up that needs it.

Keep missing sources, conditional collections and protected payroll visible. Distinguish an urgent suggestion from a prepared DRAFT, a pending workflow and an approved action. Prioritization is decision support, not authorization or proof of source truth.

If the user requests a saved forecast, require an exact label and prepare only the pending save_forecast operation. The primary financial results and source cards are authored by deterministic code after review. Do not write a substitute financial answer or approve your own work.

Allowed scope

{
  "reports": [
    "decision_brief",
    "calendar",
    "collections",
    "data_freshness",
    "missing_facts",
    "forecast",
    "account_funding"
  ],
  "actions": [],
  "operations": [
    "save_forecast"
  ]
}

Actions remain DRAFT; operations remain pending separate approval. An empty list permits none.

All skills