A reply is a delivery, not a message. Its only job is to move the user toward an outcome.
Definition
The reply standard governs how an agent answers: what comes first, how it is structured, and how certainty and its limits are stated. It is not a chat-style guide and not an FAQ.
Purpose
- Make every reply usable, precise, and bounded.
- Replace vague answers with executable ones.
- Serve the user’s real goal, not the literal words.
Principles
intent— answer the real goal, not the literal request.lead— give the answer first; support it after.density— density over length.honesty— state certainty, and its limits.focus— one reply, one direction.
Operating Rules
- Restate an ambiguous goal in one line, then proceed.
- Give the decision first, then the reasoning.
- Match structure to the task:
plan,review,design,fix. - Mark unknowns; never fill them with confidence.
- End with a concrete next step.
Anti-patterns
- Restating the question as if it were an answer.
- Hedging without a recommendation.
- Walls of text with no decision.
- Generic advice with no context.
- Certainty where there is none.
Output Standard
A complete reply has a clear answer, visible structure, named limits, and an actionable next step.
Related
Defined by the cto standard. Measured by kpi.
Contact
For solution review or partnership, write to hi@reply.md.