corporate-jargon

name

corporate-jargon

description

Transform user-supplied text into maximum-jargon, senior strategy-consulting language. Use this skill whenever a user asks for executive-ready, client-ready, board-ready, strategic, polished, corporate, business-speak, consulting-style, Big Four, or MBB-style wording, even if they do not explicitly name this skill. Preserve the source language and every supported fact, qualifier, relationship, and substantive point. Adapt the structure and format to the requested audience or, if none is given, the clearest executive-facing format. Return only the complete rewrite unless the user asks for analysis or another deliverable.

Corporate Jargon

Rewrite supplied text in an original, deliberately jargon-saturated strategy-consulting voice. Make ordinary business language sound as if it belongs in a senior consulting workstream, executive update, or client-ready document, while retaining the full meaning of the source rather than reducing it to a summary.

Process

1. Identify the text the user wants rewritten and any requested audience or format. If no source text is identifiable, ask the user to provide it.
2. Establish the source information that must survive the rewrite: facts, figures, dates, names, commitments, qualifiers, causal relationships, scope, and point of view. Preserve the source language unless the user requests translation.
3. Adapt the structure, hierarchy, and vocabulary to the audience. If no audience is specified, use a senior executive-facing consulting format.
4. Restructure freely when it improves executive readability. You may reorder, combine, or separate material and convert between paragraphs, bullets, and headings, but do not omit any substantive source information.
5. Apply dense, confident consulting language that makes the underlying content more strategic and executive-facing.
6. Perform a fidelity check before answering to confirm that the rewrite retains all source information without introducing unsupported content.

Return the full rewrite, not a summary.

Voice

Use an original general strategy-consulting voice rather than claiming the result came from, or reproducing the exact voice of, a named firm.

The default voice is deliberately maximum-jargon, not merely polished professional prose. Draw naturally from language such as:

• strategic imperatives, value creation, target state, operating model, and execution roadmap
• key levers, workstreams, stakeholder alignment, governance cadence, and cross-functional mobilization
• scalable, fit-for-purpose, end-to-end, action-oriented, and outcome-focused
• accelerate, unlock, embed, operationalize, socialize, recalibrate, and de-risk

Sustain a high density of strategic nouns, executive framing, and action-oriented verbs. Vary the vocabulary so the prose sounds intentional rather than repetitive. Jargon should elevate expression without obscuring the source meaning, introducing strategic implications, or turning a short statement into an unrelated essay.

Information Integrity And Restructuring

The rewrite may use a different structure, order, length, and format from the source, but it must retain every substantive source point. Do not introduce new facts, metrics, deadlines, owners, risks, causes, commitments, recommendations, or outcomes. In particular:

• Copy numeric values, dates, currencies, percentages, and quantities exactly.
• Preserve qualifiers such as "may," "if," "pending," "not yet," and "could." Do not convert uncertainty into certainty.
• Keep named people, teams, products, and systems unchanged unless the user asks to anonymize or rename them.
• Preserve the source's point of view and tense.
• Do not imply approval, alignment, completion, or strategic impact that the source does not support.
• Do not discard a source point merely because it seems operational, informal, or less strategic.
• Treat jargon as a linguistic transformation, not permission to invent goals, priorities, or implications. Terms such as "alignment," "value proposition," "revenue upside," and "value creation" require explicit support in the source.

When the user explicitly requests a different format, a shorter version, recommendations, translation, or a particular audience, follow that request while retaining all supported facts and avoiding unsupported additions.

Output Rules

For a standard rewrite, return the complete transformed text in the format best suited to the source and audience:

• You may reorganize the presentation, including its paragraphs, bullets, headings, and sequence, when that makes the result more executive-facing.
• Do not preface the response with "Here is the rewrite" or similar commentary.
• Do not explain word choices or summarize changes unless the user asks for them.
• Return the rewrite only, unless the user requests alternatives, rationale, or another deliverable.
• Keep non-English text in the same language and use business terminology that sounds natural in that language. Do not force English jargon into it unless the source already uses that convention.