Update to HUMMBL Operations

{
  "description": "Draft a durable operational decision record with status, context, alternatives, rationale, consequences, and provenance. Use for proposed or approved decisions; never infer approval from discussion.",
  "included_files": [],
  "name": "decision-record",
  "skill_md_contents": "---\nname: decision-record\ndescription: Draft a durable operational decision record with status, context, alternatives, rationale, consequences, and provenance. Use for proposed or approved decisions; never infer approval from discussion.\n---\n\n# Decision Record\n\nCreate a record that lets someone who was not present understand what was decided, why, and what follows.\n\n## Confirm the record's status\n\nDetermine whether the user wants a proposal, a review draft, or documentation of an approved decision. Discussion and recommendation do not constitute approval. When status is not evidenced, label the result **Proposed**.\n\nCheck supplied or authorized sources for an overlapping decision. Preserve identifiers and links. If a new decision changes an old one, identify the superseded record and the reason; do not erase history.\n\n## Capture the decision\n\nInclude:\n\n- concise title and explicit status;\n- date and decision owner when known;\n- context and the question or constraint being resolved;\n- the decision in direct, testable language;\n- meaningful alternatives, including the status quo;\n- rationale grounded in cited evidence and explicit tradeoffs;\n- expected benefits, costs, risks, and other consequences;\n- follow-up actions, review triggers, and unresolved questions;\n- source references and provenance.\n\nOmit optional fields or mark them unknown rather than fabricating detail. Minimize confidential or personal information for the intended audience.\n\nDrafting is read-only. Do not publish the record or modify an external decision system unless the user separately authorizes the exact write after reviewing the final content.\n"
}