loop-me

Original：🇨🇳 Chinese

Translated

Ask me questions within this workspace regarding the workflow requirements I want to build.

2installs

Sourcedevcxl/mattpocock-skills-zh

Added on2026-08-13

NPX Install

npx skill4agent add devcxl/mattpocock-skills-zh loop-me

SKILL.md Content (Chinese)

View Translation Comparison →

Run a stateful

/grilling

session whose only output is the workflow specification. Use the grilling discipline—relentless, one question at a time, each question with recommended answers—around the following vocabulary and goals. Create, edit, and delete specifications as the grilling resolves items.

The loop lens

A loop is a recurring pattern in a user's life: their career, their week, their morning, a repeated activity. Framing life as interlocking loops reveals how predictable their activities actually are—and that's why they're worth delegating. Use this lens to discover loops worth specifying and suggest loops the user hasn't noticed yet.

A workflow is the specification of a loop, making it tangible. You run a workflow on a loop—the loop is its running instance. Workflows live in

workflows/*.md

and are the single source of truth.

Glossary

A shared language, only used when the workflow requires it—never a checklist. Do not force any structural content: a workflow doesn't need AI, checkpoints, or schedules unless the grilling indicates it does.

Trigger — The condition that initiates each run: an event (new email, new Issue) or a schedule (every morning). Event triggers are usually more efficient.
Checkpoint — A human intervention point where the user is asked to verify or make a decision. Some workflows have no checkpoints and run fully autonomously; some don't use AI at all.
Push right — Delay checkpoints as much as possible. Do maximum preparation before involving a human, so the user only needs to be asked once at the end, with everything ready.
Brief — The content presented at a checkpoint: a compact, decision-ready summary—what was produced, why, and links to the actual output—never raw output. Users read the brief, not drafts. Review speed is critical.

Definition of Done

A workflow specification is complete when it can be built by an implementer agent without asking any questions. Keep asking questions until then; it's not done as long as there are unresolved questions.

Workspace

```
workflows/*.md
```
— One specification per workflow.
```
NOTES.md
```
— Raw notes about the user's world: the tools they use, the channels they work with, and their own terminology. When it's empty or sparse, interview them about their world before specifying anything. As terms emerge, refine vague terms into canonical ones and record them here.