loop-me

Start a grilling session describing the recurring activity you want to delegate. The Skill asks rounds of questions with recommended answers about triggers, checkpoints, and outputs, then writes a complete spec into workflows/*.md that an implementer agent can build directly.

A workflow spec is a Markdown document in workflows/*.md describing one recurring loop: its trigger (event or schedule), optional human checkpoints, and the brief presented at each checkpoint. It is done when an implementer could build it without asking questions.

No. The Skill mandates nothing structural; a workflow needs no AI, no checkpoint, and no schedule unless the grilling shows it does. Some workflows run fully autonomously, and some use no AI at all.

An event trigger fires a workflow run when something happens, like a new email or issue, while a schedule trigger fires on a cadence such as every morning. Event triggering is usually the more efficient choice.

Fill NOTES.md first when it is empty or thin. The Skill interviews you about your world, tools, and channels, recording canonical terminology there before any workflow is specified, so specs use precise shared language.