loop-me

作者: mattpocock

在这个工作区内,就我想构建的工作流程的规格向我提问。

npx skills add https://github.com/mattpocock/skills --skill loop-me

Run a stateful /grilling session whose only output is workflow specs. Use the grilling discipline (relentless, a round of questions at a time, a recommended answer attached to each) aimed at the vocabulary and goal below. Create, edit, and delete specs as the grilling resolves things.

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 an implementer agent could build it without asking a single question. Grill until then; nothing is done while a question remains.

The workspace

  • workflows/*.md: one spec per workflow.
  • NOTES.md: raw notes on the user's world, the tools they use, the channels they process, and their own terminology for both. When it is empty or thin, interview them about their world before specifying anything. Sharpen fuzzy terms into canonical ones as they surface, and record them here.

来自 mattpocock 的更多技能

writing-for-agents
mattpocock
为智能体编写文档。在创建或编辑技能,或修改AGENTS.md或CLAUDE.md时使用。
wait-what
mattpocock
等等。上一条消息没传达到——重新表述一遍。
communication
to-questionnaire
mattpocock
把你无法完全回答的决策,转化为一份供他人填写的问卷。
grill-me
mattpocock
对用户的计划或设计进行持续追问,直到达成共识,解决决策树的每个分支。当用户想要对计划进行压力测试、接受设计拷问,或提到“grill me”时使用。
researchcommunicationproject-management
tdd
mattpocock
采用红绿重构循环的测试驱动开发。当用户希望使用TDD构建功能或修复缺陷、提及“红绿重构”、需要集成测试或要求测试优先开发时使用。
developmenttesting
handoff
mattpocock
将当前对话压缩为交接文档,供其他代理接手处理。
communicationproject-managementdocument
prototype
mattpocock
在投入正式开发前,先构建一个可丢弃的原型来完善设计。在两条分支间切换——一条是可运行的终端应用,用于验证状态/业务逻辑问题;另一条是多个截然不同的UI变体,可通过单一路由切换。适用于用户希望进行原型设计、验证数据模型或状态机、制作UI草稿、探索设计方案,或提出“把这个做成原型”、“让我试试”、“尝试几种设计”等需求时使用。
developmentdesigncreative
triage
mattpocock
通过由分类角色驱动的状态机对问题进行分类。当用户想要创建问题、分类问题、审查传入的缺陷或功能请求、为AFK代理准备问题或管理工作流程时使用。
developmentproject-managementcommunication