form-generation

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This deprecated Skill prevents you from using an older form-generation workflow when you should be using the unified draft workflow instead.

Core Features & Use Cases

  • Redirect for Migration: Guides users away from legacy /form-generation usage toward the newer /draft command.
  • Unified Document Generation: Points to skills/draft/ where document generation includes form population for clinic workflows.
  • Consistent Workflow Entry: Helps keep existing integrations from breaking while signaling the correct command to use going forward.

Quick Start

Run /draft [document type] instead of form-generation.

Frequently Asked Questions about form-generation

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

FAQPage Schema
Why is my form-generation workflow deprecated for legal clinic document drafting?

Form-generation is deprecated and redirects to the unified draft workflow to ensure consistent jurisdiction-aware formatting for clinic templates like applications, answers, and petitions. You should use the /draft command instead to prevent breaking existing integrations.

How do I migrate legacy form-generation requests to the current document generation workflow?

Migrate form-generation requests by running the /draft command, which forwards operational usage to skills/draft/SKILL.md for document generation with form population. This redirect applies a mandatory deprecation notice to guide you to the new endpoint.

What's the best way to generate jurisdiction-aware petitions for a legal clinic?

The best way is using the /draft command, which replaces legacy form-generation and handles jurisdiction-aware formatting for clinic templates. This unified document generation workflow populates forms for applications, answers, and petitions.

Can I still use form-generation endpoints for applications and answers in clinic workflows?

Form-generation endpoints are deprecated and will redirect you to the /draft command for applications and answers. The migration enforces a mandatory deprecation notice while maintaining workflow entry consistency to avoid breaking existing integrations.

Does the draft workflow support form population for legacy clinic templates?

Yes, the draft workflow at skills/draft/SKILL.md fully supports form population for clinic templates including applications, answers, and petitions. It provides unified document generation with jurisdiction-aware formatting for all legacy use cases.