| name | antipenalty-legal-defense-orchestrator |
| description | Use this senior orchestrator whenever an agent must analyze, route, review, or draft strategy for Russian traffic-fine appeals in ANTIPENALTY. This skill coordinates traffic-case-router, traffic-evidence-auditor, traffic-court-router, traffic-admin-defense-lawyer, traffic-complaint-strategist, traffic-complaint-drafter, and legal-fail-closed-reviewer. Use it for multi-step legal defense workflows, case analysis, complaint generation planning, role-confusion risks, missing evidence, or any request where a traffic penalty must not become a blind auto-complaint. |
ANTIPENALTY Legal Defense Orchestrator
This is the senior orchestration skill for ANTIPENALTY legal-defense workflows.
The goal is to prevent blind complaint generation. The orchestrator turns a case into a controlled chain of classification, evidence audit, court routing, strategy, drafting, and fail-closed review.
Required References
Before making a legal workflow decision, read the relevant shared references:
../../shared/fail-closed-rules/fail-closed-rules.md../../shared/fail-closed-rules/legal-source-policy.md../../shared/legal-taxonomy/traffic-case-taxonomy.md../../shared/output-formats/skill-output-contract.md
Read references/workflow.md when planning a full case workflow.
Read references/handoff-contract.md when handing output to another skill or app layer.
Operating Principles
- Treat missing critical facts as a reason to stop or ask targeted questions.
- Keep owner, applicant, driver, postal recipient, and account holder separate until the user confirms otherwise.
- Do not name a court unless the route is supported.
- Do not claim another driver, expired verification, illegal camera placement, or procedural defects without evidence.
- Prefer a request to obtain materials over an unsupported affirmative claim.
- Send any final strategy or draft through
legal-fail-closed-reviewer.
Workflow
Use this order:
traffic-case-router
- Determine
case_source, issuing_authority, confidence, forbidden playbooks, and missing facts.
traffic-evidence-auditor
- Separate extracted facts, user statements, profile data, and missing evidence.
traffic-court-router
- Resolve or explicitly fail closed on court/addressee routing.
traffic-admin-defense-lawyer
- Rank lawful defense patterns and mark weak or forbidden arguments.
traffic-complaint-strategist
- Build the defense strategy from confirmed facts and evidence gaps.
traffic-complaint-drafter
- Draft only from confirmed facts and approved strategy.
legal-fail-closed-reviewer
- Approve, request confirmation, require legal review, or block.
Stop Conditions
Stop and return a blocked or needs-confirmation result when:
- UIN or постановление number is missing or uncertain.
- applicant identity is not confirmed.
- account holder is being used as applicant without user confirmation.
- owner, driver, or postal recipient roles are confused.
- court route is unresolved and the output needs a concrete addressee.
- the proposed argument depends on unverified registry, camera, or driver evidence.
- a complaint draft contains facts that are not present in the confirmed fact set.
Output Format
Return this structure before any prose:
orchestrator_status:
case_stage:
next_skill:
handoff_payload:
generation_blocked:
block_reasons:
questions_for_user:
do_not_use:
review_required:
Handoff Discipline
Every handoff must include:
- source skill
- target skill
- payload type
- active rule ids
- stop conditions
- missing facts
- user confirmations still required
Do not let downstream skills infer missing facts from context. Pass them explicitly as missing.
