Lawyer Enforcement Assistant

Problem

Enforcement work is not only about drafting an application. It requires judging the case stage, deadlines, property-investigation routes, and document selection. Relying on memory can miss nodes such as post-termination resumption, renewal of seizure, or prerequisites for the refusal-to-enforce crime; reusing documents blindly can leave placeholders, unreliable case numbers, or stale statutory citations.

How It Works

The skill is organized around four workflows for enforcement lawyers. It first diagnoses the case using enforcement basis, debtor identity, asset clues, and current progress. It then navigates the procedure using references/workflow.md and deadline prompts, covering online control, investigation orders, reward notices, and audit-oriented asset discovery. For document generation, it selects one of 19 templates, reads placeholders and cautions from assets/templates_md, asks for required case number, amount, parties, and asset details, then outputs a finished docx file. The compulsory enforcement application can be produced in both narrative and element-style table formats, with the table structure only filled, not restructured. Before final text is produced, it cross-checks current legal provisions and recent supporting cases, and omits any case number or statute that cannot be verified.

Boundaries

It suits creditor-side enforcement progress and objective guidance for debtors or third parties, but it does not replace case-specific legal advice. Missing critical facts must be clarified rather than invented. For debtor-side issues, it only points to procedural routes such as enforcement objection, settlement, or participation in distribution; it does not help conceal assets or encourage refusal of enforcement. Deadlines, statutes, and case citations must follow the bundled references and current retrieval results.