循环我

工程开发 社区

技能解读

当前原文的自动摘译,尚未人工审校。

环形镜头

循环是用户生活中重复出现的模式:他们的职业、他们的一周、他们的早晨、单个重复的活动。将生活想象成循环中的循环,揭示了其活动的可预测性,这就是它们值得委派的原因。使用镜头找到值得指定的循环,并提出用户没有注意到的循环。工作流程是一个循环的规范,已成为现实。您在循环上运行工作流:循环是其运行实例。工作流程存在于workflows/*.md中,是真理的源泉。

词汇

一种共享语言,仅在工作流程需要时才使用:绝不是清单。不强制任何结构性的东西:工作流程不需要人工智能,不需要检查点,也不需要时间表,除非事实证明确实如此。触发器:每次运行的触发因素、事件(新电子邮件、新问题)或时间表(每天早上)。事件触发通常更有效。检查点:要求用户验证或决定的人机循环点。有些工作流程没有,而是自主运行;有些根本不使用人工智能。

完成的定义

当实施者无需提出任何问题就可以构建工作流规范时,工作流规范就完成了。烧烤直到那时;当问题仍然存在时,什么也不做。

工作区

workflows/*.md:每个工作流程一个规范。 NOTES.md:关于用户世界、他们使用的工具、他们处理的渠道以及他们自己的术语的原始注释。当它是空的或薄弱的时候,在具体说明任何内容之前先采访他们,了解他们的世界。当模糊术语出现时,将其锐化为规范术语,并将其记录在此处。

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
工程开发
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@mattpocock · 未声明许可证
上下文用量评级
中等消耗
接入复杂程度
即装即用
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.md

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.

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。