diff options
Diffstat (limited to 'assets')
| -rw-r--r-- | assets/codex-skills/fidget-spinner/SKILL.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/assets/codex-skills/fidget-spinner/SKILL.md b/assets/codex-skills/fidget-spinner/SKILL.md index bfb0990..5f4dfbf 100644 --- a/assets/codex-skills/fidget-spinner/SKILL.md +++ b/assets/codex-skills/fidget-spinner/SKILL.md @@ -47,16 +47,18 @@ If you need more context, pull it from: - `tag.add` when a new campaign or subsystem token is genuinely needed; every tag must carry a description - `tag.list` before inventing tags by memory -- `frontier.brief.update` when the situation, roadmap, or unknowns need to change +- `frontier.update` when the objective, situation, roadmap, unknowns, or scoreboard metrics need to change - `hypothesis.record` before core-path work; every experiment must hang off exactly one hypothesis - `hypothesis.update` when the title, summary, body, tags, or influence parents need tightening - `experiment.open` once a hypothesis has a concrete slice and is ready to be tested - `experiment.list` or `experiment.read` when resuming a session and you need to recover open or recently closed state - `experiment.update` while the experiment is still live and its summary, tags, or influence parents need refinement - `experiment.close` only for an already-open experiment and only when you have measured result, verdict, and rationale; attach `analysis` only when the result needs interpretation beyond the rationale +- `experiment.nearest` when you need the nearest accepted, kept, rejected, or champion comparator for one structural slice - `artifact.record` when preserving an external file, link, log, table, plot, dump, or bibliography by reference - `artifact.read` only to inspect metadata and attachments, never to read the body - `metric.define` when a project-level metric key needs a canonical unit, objective, visibility tier, or description +- `metric.keys --scope scoreboard` before guessing which frontier-grade consumer metrics define the real hill - `metric.keys --scope live` before guessing which numeric signals matter now - `metric.best` when you need the best closed experiments by one numeric key; pass exact run-dimension filters when comparing one slice - `run.dimension.define` when a new experiment slicer such as `instance` or `duration_s` becomes query-worthy |