Skip to content
Documentation

Templates and Document Families

FieldValue
TypeSkill Resource
Source~/.copilot/skills/legal/references/templates-and-families.md
DescriptionNot specified

Source Content

Templates and Document Families

Use this reference to pick and compose the right legal document shell before drafting. This skill includes a template library of reusable shells organized by document family.

When to use templates

Use templates when:

  • The user asks for a motion, proposed order, declaration, affidavit, or discovery template.
  • A reusable shell exists for the document family.
  • The work should start from a known structure, not a blank page.
  • You need to hand off to legal for bespoke drafting after the shell is selected.

Do not use templates when:

  • No known shell fits the task.
  • The user is asking for legal advice instead of drafting help.
  • A deadline or court order creates risk that requires licensed counsel upfront.
  • The facts would require inventing authority.

Document family router

User asks forRead firstThen use
Motion, petition, rule to show cause, motion to compel, temporary reliefreferences/motions.mdclosest motion shell in templates/
Proposed order, consent order, agreed order, parenting orderreferences/orders.mdorder shell or design-system legal component
Declaration, affidavit, sworn statement, verificationreferences/sworn-statements.mddeclaration or affidavit shell
Interrogatories, RFPs, RFAs, subpoena, discovery responsereferences/discovery.mdmatching discovery template
Exhibits, appendix, evidence packet, timeline, screenshot appendixreferences/exhibits.mdexhibit packet shell or design-system exhibit components
Demand letter, settlement email, meet-and-confer, co-parent communicationreferences/communications.mdmatching communication template
NDA, MSA, SOW, loan, promissory note, release, bill of salereferences/agreements.mdmatching agreement template
Design-system legal MDX case filereferences/design-system-legal-docs.mddesign-system components and MDX rules

Workflow

  1. Identify jurisdiction, audience, document family, and intent. What is this supposed to make happen?
  2. Read the relevant reference file. Only that one file — it names the closest shell.
  3. Pick the closest bundled shell from templates/ or a design-system component named by the reference.
  4. Fill only verified facts. Mark unknowns as [FILL IN: specific fact] or [VERIFY: authority/fact].
  5. Keep the register right: Motions argue, declarations testify, orders command, exhibits authenticate, communications preserve a record.
  6. Hand off to drafting if the shell no longer fits or bespoke prose is needed.
  7. Hand off to print layout after the text is stable, if court filing or print is the goal.

Customization rules

Fill-in markers (template convention)

When you pick a template, unknowns are marked as:

  • [FILL IN: specific fact] — a fact the user must supply. Example: [FILL IN: date of the breach]
  • [VERIFY: authority/fact] — a citation or fact that needs verification before filing. Example: [VERIFY: Virginia Code § 8.01-446 statute of limitations]

The script check_legal_doc.py flags any citation-shaped string without a nearby [FILL IN: ...] or [VERIFY: ...] marker.

Register — the voice of each document type

Motions: Argue to the court. Use case names, cite authority, make an argument. “The defendant’s motion should be denied because…”

Declarations: Testify under oath. “I am the plaintiff. I know the facts of this case from personal knowledge. On January 15, 2026, the defendant…”

Orders: Command. “It is ordered that…” or “The court hereby directs…”

Exhibits: Authenticate. Narrate how you got the exhibit and why it’s reliable. “Exhibit A is a screenshot I took on March 10, 2026, of the defendant’s website…”

Communications: Preserve a record. Propose, request, or respond. “Per our phone call on March 1, 2026, I propose the following settlement terms…”

What each reference file covers

references/motions.md

Motion types (to dismiss, to compel, temporary relief, etc.), when each is used, jurisdiction-specific quirks, and the standard structure.

references/orders.md

Proposed orders, consent orders, agreed orders, parenting orders. Order shells fix the hierarchy: caption → title → findings (if any) → order → signature → date.

references/sworn-statements.md

Declarations, affidavits, verified complaints, and verification pages. Each has a standard “I am [name], I know the facts, I state as follows” opening.

references/discovery.md

Interrogatories, Requests for Production (RFPs), Requests for Admission (RFAs), responses, subpoenas. Discovery has strict numbering and formatting rules per jurisdiction.

references/exhibits.md

Exhibit packets, appendices, evidence handling, exhibit lists, authentication narration. Exhibits need a cover sheet and authentication statement.

references/communications.md

Demand letters, settlement emails, meet-and-confer letters, co-parent communications. Communications are the record of good faith; they preserve tone and offer.

references/agreements.md

Transactional shells: NDAs, MSAs (Master Service Agreements), SOWs (Statements of Work), personal loans, promissory notes, releases, bills of sale, employment letters, IP assignments.

Legal documents embedded in design-system MDX (case files, exhibits, motion briefs). This reference covers the component shapes and Markdown rules for legal-specific content.

Stop conditions

Stop and ask or escalate if:

  • Jurisdiction is unknown. Different states have different rules. Ask “What state and court?”
  • The user wants legal advice instead of drafting help. Redirect to a licensed attorney.
  • A deadline or court order creates risk. Recommend licensed counsel.
  • Facts would require inventing authority. Mark [VERIFY: ...] and flag the gap in Risk Notes.

Output contract

Always return:

  • The selected template family and shell used
  • The tailored draft or starter
  • Customization notes
  • Unresolved [FILL IN: ...] markers
  • [VERIFY: ...] flags for citations or facts
  • The recommended next handoff (drafting, layout, or attorney review)

Validate

Every template output must pass:

  • scripts/check_legal_doc.py <doc.md> exits 0 — every citation-shaped string is marked, disclaimer present.
  • Every [FILL IN: ...] is specific enough that the user knows what to supply.
  • Every [VERIFY: ...] names the exact thing that needs checking.