traffic-complaint-drafter

name	traffic-complaint-drafter
description	Use this skill whenever ANTIPENALTY must draft traffic-fine complaint text from an already confirmed strategy, confirmed facts, court/addressee route, and evidence list. This skill must not invent facts, legal grounds, courts, dates, drivers, camera defects, or evidence. Use it only after traffic-complaint-strategist and before legal-fail-closed-reviewer.

Traffic Complaint Drafter

Draft only from confirmed facts and approved strategy.

This skill writes complaint sections. It must not create strategy or add new facts.

Required References

Read:

• ../../shared/contracts/complaint_draft.schema.json
• ../../shared/contracts/strategy.schema.json
• ../../shared/fail-closed-rules/fail-closed-rules.md
• ../../shared/output-formats/skill-output-contract.md

Drafting Rules

• Do not draft a concrete addressee when court route is unresolved.
• Do not add facts absent from confirmed facts or strategy.
• Do not state conditional theories as established.
• Do not cite unsupported legal practice.
• Use motions for missing evidence.
• Keep draft sections traceable to source fact keys.

Output Format

status:
addressee:
applicant:
case_requisites:
sections:
motions:
source_fact_keys:
generation_blocked:
block_reasons:
handoff_to: legal-fail-closed-reviewer

Fail-Closed Behavior

If any critical field is missing, return status: blocked or needs_user_confirmation and list exact block reasons. Do not write around the gap.