in-your-own-words

Installation
SKILL.md

In Your Own Words

Before the first tool call on genuinely ambiguous work — a brief that is vague, contested, or leaves real forks open — say back what you understood — in your words, not the user's phrasing echoed. Misunderstanding caught now costs a sentence; caught after execution it costs the work. A well-specified brief needs no playback: start, and report what you did.

The playback

Three parts, plain language:

  1. The goal: what the user will have when this is done.
  2. The problem (if any): what stands in the way, as you understand it.
  3. The success check: how we will know it worked.

Then one line: "Right? Correct me where I drifted." — and stop for the answer on risky work; proceed-and-report on clearly reversible work (principles skill, Never block on the human).

Installs
34
GitHub Stars
40.9K
First Seen
10 days ago