plain-language-letters

Route deprecated plain-language letter requests to current client communication workflows.

Updated May 19, 2026
One-click install
npx skills add https://github.com/jrhueiueng/codex-for-legal --skill plain-language-letters-jrhueiueng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plain-language-letters
Source: https://github.com/jrhueiueng/codex-for-legal/tree/main/plugins/jrhueiueng/codex-for-legal/skills/legal-clinic__plain-language-letters
Command: npx skills add https://github.com/jrhueiueng/codex-for-legal --skill plain-language-letters-jrhueiueng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This deprecated skill helps users migrate away from an older, combined plain-language letters workflow while still pointing them to the correct newer client-facing skills.

Core Features & Use Cases

  • Legacy redirect: Guides users away from the deprecated plain-language letters entrypoint.
  • Routine correspondence routing: Directs routine updates (appointment confirmations, document requests, “we filed it” notices) to the client letter workflow.
  • Substantive status routing: Directs meaningful client status updates to the dedicated status workflow, preserving plain-language standards from CLAUDE.md.

Quick Start

Tell the assistant to use the newer routine or substantive client workflow instead of plain-language-letters.

Frequently Asked Questions about plain-language-letters

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

FAQPage Schema
How do I migrate from a deprecated plain-language legal letters workflow to a new client correspondence system?

This deprecated skill redirects requests to the correct current client communication workflows. It routes routine correspondence and substantive status updates to separate paths while maintaining plain-language standards sourced from CLAUDE.md.

When do I need to route routine client correspondence separately from substantive status updates?

Routine correspondence, such as appointment confirmations and document requests, routes to the client letter workflow. Substantive client status updates route to the dedicated status workflow to preserve plain-language standards.

Can I still use the legacy plain-language letters skill for drafting legal client letters?

The legacy plain-language letters skill is deprecated and cannot draft legal client letters. It functions solely to redirect users to the correct current client communication workflows for routine correspondence and substantive status updates.

Does the redirected client letter workflow maintain plain language standards?

The redirected client letter and substantive status workflows maintain plain language standards sourced from CLAUDE.md. Both the routine client-letter path and the status client path preserve these standards during the workflow migration.

What is the best way to handle workflow migration for legacy client status updates?

The best way to handle workflow migration for legacy client status updates is through deprecation redirects. This skill selects the correct status client path, ensuring meaningful updates bypass the old entrypoint and reach the current workflow.