菜单
Use when model obligations, owner external CodeContracts, source audits, transition cells, boundary observations, payload cases, closure targets, or ordinary test evidence need direct current comparison.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | flowguard-model-test-alignment |
| description | Use when model obligations, owner external CodeContracts, source audits, transition cells, boundary observations, payload cases, closure targets, or ordinary test evidence need direct current comparison. |
Compare model obligations, owner external CodeContract, and current tests for the same behavior and coverage.
This standalone FlowGuard satellite skill owns model_test_alignment (public_owner) rows and hands large evidence to TestMesh.
Read references/model_test_alignment_protocol.md for contracts, audits, matrices, targets, and bindings.
Accept obligations/contracts/evidence; compare bindings/freshness; block missing/stale/orphan rows and hand gaps to owners.
model-first-function-flow.ArtifactPayloadContract, owner/delegating contracts, similarity, and evidence kinds.Use only when explicitly requested or delegated by flowguard-development-process-flow's agent_workflow mode to rehearse a multi-skill, tool, plugin, or external-action workflow from a fresh inventory; generic workflow planning enters flowguard-development-process-flow first.
Use when an existing FlowGuard model and code map should drive behavior-preserving architecture contraction, including merging duplicate handlers or modules, collapsing adapters, removing dead branches, or preparing a StructureMesh refactor.
Use for external behavior registration, bidirectional source coverage, exactly one primary owner model, change-mode accounting, internal Primary Path Authority handoff, or broad done/release/archive/publish confidence.
Use when a FlowGuard model should drive pre-code module and function boundaries, FunctionBlock ownership, field/state/side-effect owners, facade design, adapter boundaries, or validation structure before production edits.
Use to generate canonical bad cases, Cartesian combinations, oracles, coverage shards, and receipts from a declared finite boundary, family seed, payload, transition, model mesh, coverage universe, or observed-problem backfeed.
Use for staged development, multi-skill work, freshness, sync, release, or final process claims.