planning-written-communication
Skill1 starsChanged 3 months agoMITView on GitHub
Use when a writing task is high-stakes, multi-stakeholder, source-grounded, or ambiguous enough that audience, objective, channel, evidence, and constraints must be resolved before drafting.
In this repository65 other files it gives its agents.
- analyzing-change-blast-radiusSkill
- analyzing-developer-career-opportunitiesSkill
- art-directing-web-interfacesSkill
- assessing-developer-proficiencySkill
- auditing-dependency-riskSkill
- auditing-pixel-perfect-frontendSkill
- bootstrapping-modern-web-appsSkill
- brag-slimSkill
- building-brand-guidelinesSkill
- building-conversion-product-pagesSkill
- building-developer-career-roadmapsSkill
- building-hybrid-game-assetsSkill
- building-premium-nextjs-interfacesSkill
- building-project-showcasesSkill
- building-regression-testsSkill
- building-reliable-node-api-boundariesSkill
- choosing-application-architectureSkill
- craft-premium-motionSkill
- creating-character-sprite-pipelinesSkill
- defining-brand-strategySkill
- designing-action-combatSkill
- designing-developer-portfolio-evidenceSkill
- designing-relational-data-modelsSkill
- designing-software-boundariesSkill
- designing-test-strategiesSkill
- designing-ui-systemsSkill
- designing-visual-identitiesSkill
- documenting-architecture-decisionsSkill
- editing-for-clarity-and-toneSkill
- engineering-gsap-animationsSkill
- evaluating-developer-proficiencySkill
- evolving-postgres-schemas-safelySkill
- humanizing-generated-proseSkill
- implementing-reference-faithful-uiSkill
- investigating-codebase-semanticallySkill
- managing-implementation-slicesSkill
- mapping-existing-codebase-structureSkill
- naming-brands-and-productsSkill
- optimizing-frontend-motion-performanceSkill
- orchestrating-cinematic-web-motionSkill
- planning-codebase-changes-with-evidenceSkill
- planning-engineering-workSkill
- planning-launch-distributionSkill
- planning-safe-refactorsSkill
- preparing-project-launchSkill
- profiling-postgres-query-performanceSkill
- reconstructing-images-as-threejsSkill
- reviewing-api-securitySkill
- reviewing-apple-platform-interfacesSkill
- reviewing-pull-requestsSkill
- reviewing-web-securitySkill
- selecting-working-methodsSkill
- shipping-github-vercel-changesSkill
- teaching-developer-conceptsSkill
- testing-integration-boundariesSkill
- testing-playable-gamesSkill
- testing-web-applications-end-to-endSkill
- threat-modeling-applicationsSkill
- tracing-code-execution-pathsSkill
- translating-figma-to-nextjsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Do not add ceremony to a simple rewrite or one-line message whose audience, purpose, and constraints are already clear.
- Distinctive: line 27
Voice constraints: use an existing brand or personal voice when supplied.
- Distinctive: line 46
If the user also asked for the final writing, hand this brief to the appropriate execution method rather than expanding this method into …
- Distinctive: line 50
Never manufacture facts, evidence, testimonials, deadlines, approvals, quotations, or user research.
- Distinctive: line 51
Do not turn uncertainty into confident prose.
- Very specific: line 52
Keep durable brand voice in writing-brand-voice-and-messaging.
- Very specific: line 53
Use writing-conversion-copy for decision-oriented marketing copy and writing-product-and-ux-copy for interface text.
- Very specific: line 54
Use editing-for-clarity-and-tone when the main input is an existing draft that already has a clear purpose.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Planning Written Communication
Overview
Turn an underspecified communication request into a compact writing brief. The output is a decision frame for another writing method, not automatically the finished message.
Use This Method When
- several audiences or stakeholders want different things;
- facts, approvals, quotes, legal wording, or source material must be protected;
- the channel or desired action materially changes the writing;
- the user asks for a communication strategy, message plan, content brief, or structure before drafting.
Do not add ceremony to a simple rewrite or one-line message whose audience, purpose, and constraints are already clear.
Build the Brief
- Audience: identify the primary reader, what they already know, what they need, and any secondary audience that changes the wording.
- Objective: state the reader outcome in one sentence: understand, decide, reply, approve, act, or remember.
- Evidence: separate supplied facts and approved claims from assumptions, missing inputs, and claims that need verification.
- Channel: record the medium, expected length, interaction model, timing, and any formatting or localization constraints.
- Voice constraints: use an existing brand or personal voice when supplied. Do not invent one when the task only needs clear communication.
- Protected material: mark quotations, citations, links, numbers, names, identifiers, legal text, code, and user-designated spans that downstream editing must preserve.
- Structure: order the minimum information the reader needs before the desired action. Put prerequisites before instructions and decisions before supporting detail when that improves scanability.
- Success check: define what a successful draft must make clear and what it must not imply.
Handoff Contract
Return a brief concise enough to use directly:
- primary audience;
- communication objective;
- known facts and approved proof;
- unresolved assumptions or verification needs;
- channel and length constraints;
- voice/tone constraints;
- protected spans;
- recommended information order;
- completion criteria.
If the user also asked for the final writing, hand this brief to the appropriate execution method rather than expanding this method into conversion, UX copy, brand voice, or general editing.
Guardrails
- Never manufacture facts, evidence, testimonials, deadlines, approvals, quotations, or user research.
- Do not turn uncertainty into confident prose; label what remains unresolved.
- Keep durable brand voice in
writing-brand-voice-and-messaging. - Use
writing-conversion-copyfor decision-oriented marketing copy andwriting-product-and-ux-copyfor interface text. - Use
editing-for-clarity-and-tonewhen the main input is an existing draft that already has a clear purpose.
Reference Signals
GOV.UK and ONS content-design guidance emphasize verified user needs, task-focused structure, plain language, and content planning before publishing. Google developer guidance reinforces audience-aware, accessible, globally understandable writing.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

