loop-me

Grills users with iterative questions to produce implementable workflow specifications.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill loop-me-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: loop-me
Source: https://github.com/MSC72m/DevForge/tree/main/skills/loop-me
Command: npx skills add https://github.com/MSC72m/DevForge --skill loop-me-msc72m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague idea for an automated workflow into a spec an implementer agent can build from is hard; this Skill runs a relentless question-and-answer grilling session until every ambiguity in your workflow design is resolved. ## Core Features & Use Cases - Stateful Grilling Sessions: Runs rounds of targeted questions, each with a recommended answer, to sharpen workflow requirements one decision at a time. - Loop Discovery Lens: Identifies recurring patterns in your career, week, or daily routines that are worth delegating and specifying as workflows. - Spec File Management: Creates, edits, and deletes workflow specs in workflows/*.md and records your terminology and tooling context in NOTES.md. - Use Case: You want to automate triaging new GitHub issues each morning. The Skill grills you on triggers, checkpoints, and briefs until a complete spec exists that an implementer agent could build without asking a single question. ## Quick Start Ask the agent to grill you about the workflow you want to build, or let it find a loop in your routine worth specifying.

Frequently Asked Questions about loop-me

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

FAQPage Schema
How do I turn a vague automation idea into a workflow spec?▼

Start a grilling session describing the workflow you want, or nothing at all. The Skill asks one round of questions at a time, each with a recommended answer, and writes the resolved decisions into a spec file under workflows/ until nothing remains ambiguous.

What is a loop in workflow design?▼

A loop is a recurring pattern in your life, such as your morning routine, weekly review, or a repeated work activity. Identifying loops reveals predictable activities worth delegating, and each workflow spec describes how one loop is run.

When is a workflow specification 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 as decisions resolve, until no open question remains about triggers, checkpoints, or outputs.

Does every workflow need AI, checkpoints, or a schedule?▼

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 autonomously, and some use no AI at all.

What is the difference between an event trigger and a schedule trigger?▼

An event trigger fires each 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.