AI Agent Skills

Prove that a knowledge base actually works before trusting it — after building or adopting docs, a knowledge graph, or a wiki, verify it can orient a fresh agent and res…

Use when evaluating test coverage gaps, planning test strategy, or assessing testing risk for code changes.

QA 流程倒数第二步的独立审查环节。在 qa-test-runner 执行完成后，以独立视角审查代码本身——检查架构、安全、并发正确性、数据一致性、 回归风险、测试覆盖缺口——不受执行方结论的影响。产出 code-review.json（含 severity 分级发现和 readiness 约束）， 和 assert-code-revi…

在风险分析完成后、写测试代码之前，生成中文业务用例并等待用户确认。这是整个 QA 流程中唯一的强制人工门禁——确认后不可回头改用例。 从 context、risk-analysis、已有用例索引出发，生成只含业务行为的 test-cases.json（不含技术检查如 Maven/build/安装）， 渲染 test-cases.html…

When asked to grill, stress-test, or pressure-test an idea, or before a decision map or spec rests on an untested conversation, interview the decision maker in small rou…

For a build brief, implementing a spec or tracked item, or mid-build discoveries tempting scope expansion, build thin verified slices with test-first checks at named bou…

挖掘用户真正想要的东西，而不是他们觉得自己“应该”要的东西。实现方式是一次一问的访谈，直到对底层意图达到约 95% 的置信度。当一个请求信息不全时（"build me X" 却没说 "for whom" 或 "why now"）、当用户明确发出邀请（"interview me"、"grill me"、"are we sure?"、"st…

Compare two versions of an LLM-directed document - an original (teacher) and a candidate (student) - across a transfer set and return a per-case behavioural-equivalence…

Systematic workflow for identifying coverage gaps and writing missing tests. Use when coverage is below target or the user asks to improve coverage.

Optimizes multi-step conversion flows including signup, onboarding, upgrade, and checkout. Maps each step, identifies friction and drop-off risks, then recommends specif…

Deep research producing a fully written, source-validated literature review on an agricultural question, as a senior agricultural scientist of the relevant discipline: s…

General-purpose deep research that produces a fully written, source-validated literature review on any question: scope it, design the method, discover and screen sources…

缺陷修复方法论唯一入口：口喷 bug 定位直修；implement-test-review 循环内的反馈修复也走本 skill（循环内分支，原 impl worker 执行）。触发：修 bug / 有个 bug / 报错了 / 行为不对 / fix / /eo-fix。 NOT FOR: 明确的业务变更（走 /eo-change）。

按 change.md 的 TODO 分批落地代码，批末自验对应 AC。触发：实现 / 写代码 / implement / /eo-implement。 NOT FOR: bug 与反馈修复（口喷 bug 与 test/review/acceptance 循环内反馈一律走 /eo-fix）；变更起草（走 /eo-change）。

eo 流程总控：按用户意图圈一段（入口节点 → 出口节点 → 收敛标准），把 eo-change / eo-implement / eo-archive 及可选闸门（eo-change-review / eo-test / eo-review）派发到可插拔执行基底上推进至收敛，窗口化汇报进度。触发：eo-loop / 串起来跑 / 循环…

按需独立测试视角：风险信号命中或用户点名时，对已实现 change 做测试审计、补缺与重验证，产简版 test.md。严禁修改业务代码。触发：找双新眼睛跑测试 / 独立验证 / 给这个 change 补测试 / /eo-test。 NOT FOR: 与 change 无关的日常跑测试或补单测（直接做即可，不产报告）；默认主路的自验（归…