What problem does it solve?
Law firms tracking cases across scattered notes and ad-hoc YAML files end up with format drift, lost deadlines, and no single source of truth for tasks, deadlines, and case stages. This Skill provides one authoritative write engine for case.yaml files so every status change is validated, auditable, and protected against accidental overwrites of lawyer-entered data.
Core Features & Use Cases
- Single write engine CLI: show, list, add-task, set-status, add-deadline, set-stage, set-fields, validate, migrate, render, log-work, and backfill-work subcommands with schema validation, file locking, and atomic writes.
- Human override protection: row-level source tracking (user vs ai), locked procedure stages, and a rule that closed cases are only marked manually, so AI agents never overwrite lawyer decisions.
- Derived views and work logs: renders one-page Markdown/HTML case views that auto-refresh on every write, plus structured billable work records with auto-estimated durations.
- Use Case: After drafting a defense statement, an agent runs the closing sync flow: it loads the case state, registers the new filing deadline with its legal basis, marks the drafting task done, logs 1 hour of work, and validates the file before reporting changes.
Quick Start
Ask the agent to show the current status of case 250609-A and then add a task to draft the appeal brief with a deadline of 2026-09-15.