form-generation

Redirect legacy form-generation workflows to the /draft command.

Updated May 15, 2026
One-click install
npx skills add https://github.com/az9713/claude-for-legal-tutorial --skill form-generation-az9713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: form-generation
Source: https://github.com/az9713/claude-for-legal-tutorial/tree/main/legal-clinic/skills/form-generation
Command: npx skills add https://github.com/az9713/claude-for-legal-tutorial --skill form-generation-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This deprecated skill helps you recognize and understand the older form-generation workflow so you can migrate to the newer clinic document generation approach.

Core Features & Use Cases

  • Redirect for migration: Points users away from the legacy form-generation path and toward the replacement skill.
  • Practice-area document generation: Covers first-draft generation for clinic documents, including form population, using practice-area templates and jurisdiction-aware formatting.
  • Backward compatibility: Keeps the old entry point available for existing integrations.

Quick Start

Use /draft [document type] instead of invoking this legacy form-generation skill.

Frequently Asked Questions about form-generation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate first-draft legal clinic documents like asylum applications or eviction answers?

To generate first-draft legal clinic documents, use the /draft command to populate practice-area templates with jurisdiction-aware formatting for asylum applications, eviction answers, and protective order petitions. This routes workflows to the newer draft-based generation flow.

Why should I migrate from legacy form generation to the draft-based workflow?

You should migrate from legacy form generation to the draft-based workflow because the older skill is deprecated. The newer /draft command handles clinic document workflows and form population using practice-area templates across jurisdictions.

What's the best way to create jurisdiction-aware legal forms for a legal clinic?

The best way to create jurisdiction-aware legal forms is to invoke the /draft command with your specified document type. This applies practice-area templates to format clinic documents correctly across jurisdictions.

Can I still use the old form-generation skill for clinic document workflows?

The old form-generation skill remains available for backward compatibility with existing integrations. However, it is deprecated and simply redirects you to follow the workflow defined in skills/draft/SKILL.md.

Does the clinic document generation flow support protective order petitions across jurisdictions?

Yes, the clinic document generation flow supports protective order petitions across jurisdictions. It uses the /draft command to apply practice-area templates and populate forms for clinic use cases.

How do I start drafting practice-area documents for legal clinic use cases?

To start drafting practice-area documents, use the /draft command with the specific document type. This initiates the workflow defined in skills/draft/SKILL.md to generate first-draft documents with form population.