Tri-Lingual Mode

Problem

When explaining the same technical plan to a CEO, a business VP, and a new engineer, the gap is rarely missing facts. It is usually a mismatch of perspective: builders care about implementation, risk, and dependencies; decision-makers care about cost, timeline, and value; newcomers need a clear mental model first. Tri-Lingual Mode rewrites one source into audience-specific versions instead of simply shortening it.

How It Works

The skill outputs an executor version, a decision-maker version, and a newcomer version by default, and it also supports a single audience or a custom role. Key steps include:
- Perspective translation: preserve key facts, constraints, assumptions, and decision points while changing wording, structure, and emphasis.
- Coverage check: detect missing numbers, risks, dependencies, or approval items and flag or restore them.
- Analogy matching: choose analogies from the target audience's familiar world, avoiding jargon that would confuse the reader.
- Follow-up prediction: list the three questions each audience is most likely to ask after reading.
It also enforces hard constraints: wording changes, but facts do not; the three versions remain informationally symmetric; key numbers stay explicit; and conflicting audience needs are not forcibly blended.
It fits reporting, email drafting, pitch preparation, and onboarding explanations. The boundary is explicit: it does not invent information, does not validate the correctness of the plan, and does not perform cross-language translation. If the source is too short, the role is ambiguous, or the content contradicts itself, it prefers clarification over producing a one-size-fits-all rewrite.