Menu
Use when retikz alpha implementation tests have passed but red or yellow changes still need adversarial validation against edge cases, JSON IR stability, and contract robustness before documentation.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when changing any retikz apps/docs content, route data, i18n, demo, SourceLinks, or schema reference before loading the matching page-type skill.
Use when retikz needs multiple independent LLMs to review the same fixed code, ADR, implementation plan, test contract, commit, or working-tree snapshot before a gate or delivery decision.
Use when an Alpha ADR needs a pre-implementation capability gate, or a Beta milestone needs code-based completeness and package-boundary auditing.
Use when planning a retikz architecture direction, version roadmap, or alpha feature that may need a long-lived ADR before implementation.
Use when retikz work is primarily refactoring, reorganization, renaming cleanup, modularization, or internal simplification and should start from a reviewed implementation plan before code changes.
Use when retikz implementation, adversarial testing, and docs are complete, and an ADR or beta TODO needs changelog, contract consistency review, roadmap status updates, or final human acknowledgement.
| name | develop-test |
| description | Use when retikz alpha implementation tests have passed but red or yellow changes still need adversarial validation against edge cases, JSON IR stability, and contract robustness before documentation. |
实现测试全绿后，继续从“构造会让实现挂的输入”角度找 bug。red / yellow 必走，green 跳过。
Proposed。tsc --noEmit / vitest 已通过；否则回 develop-implement。先读取测试契约矩阵，优先攻击其中的不变量与反例；不要把自测退化为重复 happy path。
优先找破坏 AI 友好契约的问题：
再查常规边界：自引用 / 引用环、0 / -0 / NaN / Infinity / 极值、长字符串 / Unicode id、深层嵌套、默认值边界、与已有功能交叉。
优先用独立线程、子代理或外部模型当 Bug Hunter；不可用时主 AI 自己执行并说明退化。
Bug Hunter 只做三件事：
tests/_scratch/ 写 adversarial Vitest case，并用 pnpm temp:test -- --workspace <workspace-directory> --file <tests/_scratch/*.test.ts> 运行。| 结果 | 处理 |
|---|---|
| BLOCKING | 提升为正式回归测试，回实现阶段修；修完重跑本阶段 |
| WARNING | 主 AI 判断本 ADR 内修还是记 backlog / roadmap |
| INFO | 作为 wrapup changelog 或汇报素材 |
同一 BLOCKING 最多修 3 轮；仍不收敛则 halt 给人工。
develop-document / develop-wrapup 使用。