360 Secure SkillHub
360 安全技能中心

find-the-exceptions

该 Skill 将现有 happy-path 规则、决策表、SOP 或业务流程拆解决策变量，按边界、输入、时序、权限、生命周期、范围、依赖失败和规则冲突等视角生成候选例外，筛选会实质改变结果的例外，并输出含预期路径、例外路径、状态和待决证据的决策表；未解决的支路标记为 UNKNOWN。

raguets
raguets
热度 18.02
最近更新 2026-09-04 00:52:41
分类：效率依赖：纯提示词应用场景：工作流 / 模板 / 报告撰写

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add find-the-exceptions
Metadata
name
find-the-exceptions
description
Part of the Overpowered skill suite. Pressure-test a rule, decision table, SOP, requirement, or business process by finding edge cases and alternative branches that would break a happy-path specification. Use before automation or formalization when hidden exceptions could change behavior; focus on material exceptions, not imaginative trivia.
metadata
{"suite":"overpowered","suite_url":"https://github.com/raguets/overpowered","level":"2-process","version":"0.1.0"}

Overpowered / Find the Exceptions

Core rule

A process is not executable until its material non-happy paths are either defined or explicitly unknown.

Procedure

  1. State the current happy-path rule/process in precise terms.
  2. Identify its decision variables: amount, role, state, timing, availability, jurisdiction, data quality, dependencies, etc.
  3. Generate candidate exceptions using these lenses:
    • boundaries: exactly at thresholds, empty/zero/max values;
    • missing/invalid/duplicate inputs;
    • timing: late, early, concurrent, reordered events;
    • authority: absence, delegation, multiple approvers;
    • lifecycle: cancellation, amendment, retry, rollback;
    • scope: internal/external, special category, jurisdiction;
    • dependency failure: unavailable system/source/person;
    • conflicting rules or precedents.
  4. Filter to exceptions that can materially change the outcome.
  5. Resolve discoverable facts from available artifacts before asking the user.
  6. Convert resolved branches into a decision table/state model.
  7. Mark unresolved branches UNKNOWN; do not invent policy.

Output contract

Condition | Expected path | Exception path | Status | Evidence / decision needed

End with:

  • newly discovered rules;
  • unresolved branches that block automation;
  • edge cases that are safe to defer.

Deep reference

Read references/exception-lenses.md for complex processes or when the first pass does not expose enough material branches.

Interaction rule

When user input is required, ask one high-value question at a time. Prefer a recommended/default answer when there is enough context to propose one.

Gotchas

  • Do not confuse brainstorming bizarre scenarios with finding material exceptions.
  • Do not ask humans for facts the environment can provide.
  • Exact-threshold behavior is a common source of automation bugs; make it explicit.
  • Exceptions can modify data shape, authority, timing, or failure recovery—not only business rules.

Stop condition

Stop when material branches are defined, deliberately deferred, or explicitly unknown with an owner for resolution.