🗣️ Communication & Mastery
The same idea needs to reach the director, the team, the beginner, and the partner— without changing the content. And the 100 commands need three that operate on them: /mode, /chain and /preset. It’s family 10, divided into communication and meta-commands.
By the end of the track, you’ll turn an analysis into the right four messages for four readers, and build chains and presets that make language work for you.
The track’s rule: form adapts to the reader, content doesn’t; and a named chain is worth more than a repeated prompt.
Course roadmap
🗣️ Communication and learning
From /brief to /audience: executive summary, explanations by level, progressive teaching, translation, rewriting, and format — plus a pipeline and a workshop.
🎛️ Meta-commands and mastery
From /mode to /preset: the 3 meta-commands, the 5 official recipes, a command’s YAML structure, precedence, and the v0.2 roadmap.
Detailed content
🗣️ Communication and learning
The 7 communication commands in family 10 — plus the pipeline that links them and a hands-on workshop.
Deliver only what’s essential: minimum context, decision, evidence, risks, and next action—all on one screen.
Whoever decides won’t read 6 pages. Either you make it concise, or the decision gets made based on what the person remembers from the title.
essential context · decision · evidence · next action.
Adapts depth and vocabulary to the audience’s level and uses examples when they improve understanding.
Explaining at the wrong level is the main cause of “I get it” when someone doesn’t. Too shallow is insulting; too deep loses people.
stated level · calibrated vocabulary · example when helpful.
Organizes concepts, intuition, examples, practice, common mistakes, and learning checks — the sequence that helps knowledge stick.
Explaining transfers information; teaching ensures it sticks. The difference is practice and verification—neither of which /explain provides.
intuition before definition · practice · common mistake · verification.
/translate preserves meaning, tone, and technical terms, adapting only what’s necessary for the target language; /rewrite preserves the essential content and optimizes clarity, tone, persuasiveness, or concision for a stated goal.
A literal translation loses the tone; a rewrite without a goal loses the point. Both commands protect the intent while changing the surface.
intent preserved · technical term retained · rewrite objective.
Converts the same information into a table, JSON, checklist, memo, script, or another requested format—without adding or removing content.
The right format gets information used: a table to compare, a checklist to execute, JSON for a machine to read. The right content in the wrong format dies in the inbox.
same information · format for use · no new content.
Adjusts language, examples, depth, anticipated objections, and calls to action for a defined audience.
The same proposal convinces the finance team for one reason and the technical team for another. Send both the same text, and you’ll convince neither.
defined audience · anticipated objections · CTA by audience.
The communication chain: first compress (what’s essential), then calibrate depth (for what level), then adapt (for whom, with what objection and CTA).
The order matters: adapting before compressing wastes effort on content that will be cut; compressing after adapting cuts the adaptation.
compress → calibrate → adapt · output handoff · one chain, three audiences.
Practical exercise: take a real decision email and produce four versions—a brief for the approver, an explanation for the person carrying it out, a checklist for the operator, and a translation for the external partner.
It’s proof that you’ve mastered the family: the content doesn’t change across the four versions, and each one serves a different reader.
invariant content · four formats · cross-check.
🎛️ Meta-commands and mastery
The 3 meta-commands in family 10, the document’s compound recipes, and the language’s internal structure.
Activates a persistent behavior profile for the current execution — conservative, exploratory, executive — that all subsequent commands inherit.
Repeating “be conservative” in every command is noise. /mode declares it once and stays in effect until changed.
persistent profile · inherited by commands · explicit switching.
Runs commands in an explicit order, passing relevant output from one to the next—the difference between chaining commands and a real pipeline.
Inline composition (/truth /gaps /rank) runs everything on the same input. /chain makes each command work on the previous command’s result—that’s where language becomes a system.
explicit order · output becomes input · auditable pipeline.
Expands a short name into a predefined chain of commands with parameters—the chain you use every week becomes a single word.
Every team repeats the same 4-5 chains. Naming them standardizes the process and eliminates variation from someone who "forgot /pushback".
short name · predefined chain · embedded parameters.
The five chains the document recommends as standard compositions: reliable decision-making, product development, agent architecture, project execution, and business thesis.
They’re the map of the entire course in five lines—each one spans 3 to 4 tracks. Master all five and you master the language.
decision · product · agent · execution · business thesis.
The nine-field framework the document suggests for defining any command: name, family, version, purpose, inputs, tools, rules, output schema, acceptance, and fallback.
It’s what makes the language implementable: an agent can read the YAML and know exactly what the command requires, produces, and does when it fails.
output_schema · acceptance · fallback · versioning.
The rule that decides what takes precedence when a /mode says “conservative,” a /preset includes “exploratory,” and an explicit parameter says something else: the most specific one wins.
Without formal precedence, behavior depends on the order in which you typed things—and two users get different results from the same commands.
specific beats generic · parameter > command > chain > preset > mode.
What the document acknowledges as pending: aliases, parameter types, output schemas, formal precedence, permission levels, tool policies, official presets, and conformance tests.
Knowing what the language still doesn't guarantee is part of mastering it—and it's where those who've made it this far can contribute.
aliases · types · formal precedence · permissions · compliance.