{"id":76454,"plugin_id":"plugin_asdk_app_6ad61143c49c8191941ab91d243863e7","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-02T18:12:24.507Z","digest":"070d9bc0997a782862fbe418e66d59651ded7de8525c4103e1c18ccc2439c148","against":null,"payload":{"description":"Where this case stands: what is done, what blocks it, and the single next action","included_files":[],"name":"case-brief","skill_md_contents":"---\nname: case-brief\ndescription: 'Where this case stands: what is done, what blocks it, and the single next action'\nmetadata:\n  title: 'Case Brief'\n  category: cases\n  order: '7'\n  plugin: 'true'\n---\n\nNo case in context: ask which case, or find it with query_entities, before anything else. 1. Start from the case context, then query_entities on checks, with a case__default__id rule for this case since it reads the whole workspace, and get_check on every check that is not approved, so you read the real result and any review comment. 2. list_case_controls and list_notes. 3. Report: status, risk, template, assignee on one line; what is done; what is blocking — each non-approved check with type, entity, status and the concrete reason from its result, cited not paraphrased, then each incomplete manual control; what is missing that nobody has requested; one next action and who must do it. Link every entity you name. If the next step is a human decision, say so — never invent an escalation path you have no tool for.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}