메뉴
Use when a retikz ADR or beta TODO changes data structures, public interfaces, compile semantics, adapter behavior, renderer output, or docs-visible behavior and needs a traceable behavior-to-test contract before implementation or final acceptance.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
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.
SOC 직업 분류 기준
| name | test-contract |
| description | Use when a retikz ADR or beta TODO changes data structures, public interfaces, compile semantics, adapter behavior, renderer output, or docs-visible behavior and needs a traceable behavior-to-test contract before implementation or final acceptance. |
把已确认的设计行为转成可观察契约。实现可以自由重构；只要每项契约仍有足够的测试证据，内部细节不构成验收对象。
| 场景 | 用哪个 skill |
|---|---|
| 从 ADR / TODO 定义行为和测试证据 | test-contract |
| 审计历史测试是否重复或过期 | test-review |
| 主动构造异常输入寻找缺陷 | cross-test / develop-test |
| 实施已接受的测试整理 | develop-refactor |
本 skill 不决定产品设计、不写实现或临时探索测试，也不以覆盖率百分比代替契约。
Alpha 读取长期 ADR 与镜像 PLAN.md；Beta 读取 TODO / plan。再读取公开类型或 schema、相关实现边界、已有测试与 docs 页面。把详细矩阵写入与 ADR / TODO 同构的 ignored plan：
packages/viz/_notes/decisions/chart/v0/v0.1/alpha.1/01-example.md
-> packages/viz/_notes/plans/chart/v0/v0.1/alpha.1/01-example/TEST_CONTRACT.md
长期 ADR 只保留稳定测试策略摘要和关键不变量，不保留逐项 case、文件索引、路径、命令或执行清单。TEST_CONTRACT.md 与其它 plan 文件默认不 stage、不 commit。
每行必须使用行为名称，而不是 ADR 编号、内部函数名或历史阶段名：
| 行为 | 可观察输入/输出 | 不变量 | 反例 | 最低层 | 上层证据 | 正式测试证据 | 验证命令 / 页面路径 | 状态 |
|---|---|---|---|---|---|---|---|---|
| React 与 Vanilla 表达同一节点 | 两入口产出等价 IR | 默认值一致 | 无效 prop 可诊断 | adapter parity | docs demo | tests/...: case | pnpm --filter ... test:changed | 已覆盖 |
| 行为边界 | 最低层 | 必要时追加 |
|---|---|---|
| schema、默认值、JSON、错误 | schema / parser | compile |
| IR 到 Scene、引用、几何 | compile contract | renderer |
| React / Vanilla 同能力 | adapter parity | compile |
| Scene 到 SVG / Canvas | renderer contract | 小型 golden |
| docs 示例、控件、错误展示 | component integration | page / browser |
优先在最低能证明行为的层测试；只有用户路径、跨层组合或真实 DOM / 路由才提升到 docs 或页面测试。Snapshot 只在它能表达用户可见语义时作为证据。
PLAN.md 没有重定义它们。develop-implement；实现后为每行填写正式测试证据、验证命令或页面路径，以及已覆盖 / 接受风险状态。发现问题时写入正确真源：
PLAN.md / TEST_CONTRACT.md；物质性改变计划后重新执行 Plan Gate。