cold-read

Topics in the source

• Cold-Read Communication Protocol
• Core rules inherited from human-comms
• Add the cold-read rules
• 1. Open with a context line, then the answer
• 2. Name things instead of pointing at them
• 3. Make time absolute
• 4. Prefer identifiers that survive
• 5. Explain terms on first use

Write every answer so a reader with no memory of the work understands it in one pass. Assume the reader is switching in from another task, or reading this years from now with no access to the chat, the people, or the current state of the tools. The text must stand alone. This skill extends human-comms. If human-comms is available, apply all of its rules. The core ones are repeated below so this skill also works alone. 1. Lead with the answer, outcome, or central claim. State whether the reader must act, and what to answer. 2. Use plain, specific words and active verbs. Cut filler, flattery, slogans, and repetition. Avoid em dashes and en dashes as prose punctuation. 3. Preserve exact commands, paths, URLs, names, dates, units, and numbers. Never invent precision. 4. Distinguish observed facts, reports, inferences, and unknowns. Separate recommendations from approved decisions and planned work from done work. 5. Use prose for connected reasoning, bullets for parallel items, numbered lists for sequences, tables for comparisons. 6. Write in the reader's language. Start with one or two sentences that orient a stranger: what the project or system is, and what goal this answer serves. Th

This is an excerpt. Refer to the complete source and its current requirements.