菜单
Use when implementing, writing tests, modifying tests, reviewing tests, fixing bugs, or changing business logic, reports, data models, APIs, auth, UI flows, jobs, or integrations where tests must prove user or business behavior rather than implementation details.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when adding or modifying a hook, gate, denial/permission message, or waiver/exemption/override path; when deciding whether to keep, revise, or retire a rule or gate; or when auditing a gate or triaging a complaint that a gate causes friction. The implementation manual for building gates that are enabling not coercive — escape paths, persistent signal, value-not-presence validation, with audit-validated reference designs and anti-patterns.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
| name | behavioral-test-oracle-review |
| description | Use when implementing, writing tests, modifying tests, reviewing tests, fixing bugs, or changing business logic, reports, data models, APIs, auth, UI flows, jobs, or integrations where tests must prove user or business behavior rather than implementation details. |
Use this before implementation for non-trivial changes where a superficial test could pass a fragile implementation.
Produce a Test Oracle Brief:
Reject the test plan if the named fragile implementation would pass every relevant behavioral, fixture, contract, architecture, and static check.
Before implementation begins, state:
