Turn recurring activities into workflow specifications through a focused interview. The skill clarifies triggers, human review points, and working terminology, recording enough detail for an implementing agent to build the workflow without further questions.
在这个工作区中，就我想构建的工作流规格访谈我。
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
调用 Skill 工具并指定 grilling，运行一个 stateful session，唯一输出是 workflow specs。使用 grilling discipline：持续追问、一次一个问题、每个问题都附推荐答案。围绕下面的 vocabulary 和 goal 来访谈。随着 grilling 解决问题，创建、编辑、删除 specs。
Loop 是用户生活中的重复模式：career、week、morning，或单个重复活动。把生活看成 loops within loops，会揭示活动到底有多 predictable，也因此揭示哪些值得 delegating。用这个 lens 找到值得写 spec 的 loops，并提出用户尚未注意到的 loops。
Workflow 是一个 loop 的 spec，并让它变得可执行。你在 loop 上运行 workflow；loop 是它的运行实例。Workflows 存在 workflows/*.md 中，并作为 source of truth。
只有当 workflow 需要时才使用 shared language；它不是 checklist。不要强制任何结构：除非 grilling 表明需要，否则 workflow 不需要 AI、不需要 checkpoint，也不需要 schedule。
当 implementer agent 能在不问任何问题的情况下构建它时，workflow spec 才算 done。持续 grilling 到那时；只要还有问题，就不算完成。
workflows/*.md - 每个 workflow 一个 spec。NOTES.md - 关于用户世界的 raw notes：他们使用的 tools、处理的 channels，以及他们对两者的自有术语。当它为空或很薄时，先访谈用户的世界，再写任何 spec。随着 fuzzy terms 浮现，把它们打磨成 canonical terms，并记录在这里。No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Find the right skill and sequence for your current development task, from shaping an idea to implementation, debugging, and review. The guide also explains when to prototype, prepare specifications, or move work into a fresh session.
Summarize the current conversation and launch a fresh background agent to continue the work. The handoff includes references to existing artifacts and suggested skills, removes sensitive information, and can emphasize the next session’s intended focus.
Review changes from a chosen Git reference against both project coding standards and issue or specification requirements. Separate parallel reviews report rule violations, possible design problems, missing requirements, and changes beyond the intended scope.
Design modules that expose simple interfaces while hiding substantial behavior. Use shared terms and principles to assess interface complexity, decide where behavior can be swapped, and organize code so callers and tests use the same interface.
Diagnose difficult bugs and performance regressions by first building a repeatable check for the exact symptom. Minimize the reproduction, test ranked hypotheses, apply a fix, and verify the original scenario with regression tests where suitable.
Clarify project terminology and the relationships between business concepts. Check definitions against concrete scenarios and code, update GLOSSARY.md as terms are agreed, and record significant design decisions with their trade-offs when the stated criteria are met.