← DotfileCONTENT HISTORY
WHAT CHANGED
Update to Dotfile
Snapshot Nov 2, 2026 · 18:12 UTC · version 2026.10.301142
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Dotfile and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"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"
}SHA-256 of public snapshot: 070d9bc0997a782862fbe418e66d59651ded7de8525c4103e1c18ccc2439c148