Command Explorer › re: — the reply's form › steps

re:steps

A numbered procedure, one action per step.

Level 2Structure axisClass: actShortest: stRequires: nothing beyond conversationPersistence: noneConfirmation in the reply: not required

Directive Shorthand 3.2 · Command explorer · Assembled from the canonical spec, registry, usage guide, and implementation guide — this page adds no meanings.

In the re: domain re:voice — Reply with a voice note (spoken audio).re:show — Answer visually instead of in prose.re:recap — Catch me up: state, decisions, what's open.re:steps — A numbered procedure, one action per step.re:list — Present the material as an enumerated set — items on their own lines, each one complete; the form for a set, where steps is the form for a sequence.re:cite — Show this reply's sources, inline with its claims.

What it does

The how-to shape: a numbered list of actions, one per step, executable in order. No essay.

The registry's own words: A numbered procedure, no essay: the how-to shape, one action per step.

Fire it — usage examples

“How do I reset the router? re:steps”

→ prerequisites first, then numbered actions, each one something you can do and check off.

An agent explains a repair in three paragraphs of prose. Quote it and reply: re:st

→ the same content re-cut as numbered actions, in the order you'd do them.

Said aloud: “Lingo, reply steps — resetting the router.”

→ the procedure, numbered, no essay.

Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “reply steps”. Dictated directives fire deliberately, never by accident.

What the agent actually does

The answer is reorganized into execution order; a decision point becomes an explicit conditional step (“if X, do Y; otherwise continue”). Numbering paragraphs of prose instead is a failed re:steps.

The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-re-steps ↗.

When the host can't

No host capability required; always executable.

Conformance — “done when”

The reply is a numbered action sequence, executable in order, with at most one framing line.

Persistence class: none. Execution report in the reply: not required. A user can test any of this by hand — fire the directive, then check the result against the store, the schedule, or the reply itself.