2.5 KiB
name, description
| name | description |
|---|---|
| loop-me | Grill me about specs for the workflows I want to build, within this workspace. |
Run a stateful /grilling session whose output is workflow specs. Use one question at a time with a recommendation, focused on the requested workflow. Update relevant specs as decisions resolve; preserve unrelated specs and remove an existing one only when the user has authorized that scope change.
The loop lens
A loop is a recurring pattern in the user's life: their career, their week, their morning, a single repeated activity. Picturing a life as loops within loops reveals how predictable its activities really are — which is what makes them worth delegating. Use the lens to find loops worth specifying, and propose ones the user hasn't noticed.
A workflow is the spec of one loop, made real. You run a workflow on a loop — the loop is its running instantiation. Workflows live in workflows/*.md and are the source of truth.
Vocabulary
A shared language, reached for only when a workflow calls for it — never a checklist. Mandate nothing structural: a workflow needs no AI, no checkpoint, and no schedule unless the grilling shows it does.
- Trigger — what fires each run: an event (a new email, a new issue) or a schedule (every morning). Event-triggering is usually the more efficient.
- Checkpoint — a human-in-the-loop point where the user is asked to verify or decide. Some workflows have none and run autonomously; some use no AI at all.
- Push right — defer the checkpoint as far as it will go. Do maximal work before involving the human, so they are asked once, late, with everything prepared.
- Brief — what a checkpoint presents: a tight, decision-ready summary — what was produced, why, and a link down to the asset itself — never the raw output. The user reads a brief, not a draft. Speed of review is imperative.
Definition of done
A workflow spec is done when its scope, inputs, outputs, authority, failure handling, and acceptance criteria are actionable. Record safe assumptions and optional future questions; keep interviewing only about decisions that materially affect the requested workflow.
The workspace
workflows/*.md— one spec per workflow.NOTES.md— relevant tools, channels, preferences, and terminology already learned. Missing notes do not block a clear request; ask only for context needed by this workflow and avoid collecting unrelated personal details.