bro

Give a capable engineer a terse, jargon-free briefing on the critical facts and implications of an effort before it is built or after it is completed. Use when the human explicitly invokes $facts, and never otherwise; do not invoke this skill automatically.

Render one lane of work as a vertical progress ladder in the terminal, done on top and todo below, read top to bottom.

Clearly restate a human's request so they can confirm alignment before work begins. Use when the human explicitly invokes /readback or $readback after a long, dictated, unclear, or complex prompt; never invoke automatically.

Give a two- or three-sentence recap of the latest work in the current session.

Render the state of the work in flight as an ASCII status board in the terminal, instead of a status paragraph.

Restate the last message in plain human language, with no jargon.

Get an independent decision from a fresh agent that receives a neutral brief and none of the current conversation.