loop-me

Grills users one question at a time to produce workflow specification files.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/j172/bid --skill loop-me-j172
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-me
Source: https://github.com/j172/bid/tree/main/agent/skills/loop-me
Command: npx skills add https://github.com/j172/bid --skill loop-me-j172

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning vague ideas about recurring personal workflows into precise, implementable specs is hard; this Skill runs a structured grilling session that interrogates you until each workflow spec is complete enough for an implementer agent to build without asking questions. ## Core Features & Use Cases - Loop discovery: Identifies recurring patterns in your career, week, or day that are worth delegating, including loops you have not noticed. - Stateful grilling sessions: Asks one question at a time with a recommended answer attached, creating, editing, and deleting specs in workflows/*.md as answers resolve. - Shared vocabulary: Applies concepts like triggers, checkpoints, push-right, and briefs only when a workflow genuinely calls for them. - Use Case: You want to automate your morning email triage. The Skill interviews you about your tools and channels, records terminology in NOTES.md, and produces a complete spec in workflows/email-triage.md defining the trigger, checkpoint, and brief format. ## Quick Start Start a grilling session to spec out the recurring workflows in my week that I could delegate.

Frequently Asked Questions about loop-me

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a workflow specification for automation?

Start a grilling session that asks one question at a time about your recurring loop, its trigger, and its checkpoints. The session writes the resolved spec into workflows/*.md, iterating until an implementer could build it without asking anything.

What is a loop in workflow automation?

A loop is a recurring pattern in your life, such as your morning routine or weekly review, that is predictable enough to delegate. A workflow is the written spec of one loop, and running the workflow on the loop is its instantiation.

Does every workflow need AI or a human checkpoint?

No. The vocabulary 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.

What is the difference between event and schedule triggers?

An event trigger fires on something happening, like a new email or issue, while a schedule trigger fires on a cadence like every morning. Event triggering is usually the more efficient choice.

When is a workflow spec considered done?

A spec is done when an implementer agent could build it without asking a single question. The grilling continues, creating and editing specs, until no open questions remain.