embedeval: Command for Claude Code

/negatives — Interactive mutation-oracle authoring

Communication Protocol

• Be direct. No preamble, no ceremony, no encouragement.
• Show the user concrete content (code, check names, reference snippets) before asking questions.
• Ask ONE decision per AskUserQuestion call — never batch multiple unrelated decisions.
• Never guess judgment calls. If unclear, ask.
• Never skip the oracle gate. A negative that doesn't pass oracle is not landed.

Sequentially author negatives.py for every case that lacks one, with interactive judgment gates where LLM cannot reliably decide.

---

Usage

/negatives                         # sync + resume — work the next pending case
/negatives --status                # sync + print progress table and exit
/negatives --case TC_ID            # sync + work a specific case
/negatives --category dma          # sync + cycle pending cases in a category
/negatives --sync                  # ONLY reconcile progress file with cases/, print diff, exit
/negatives --skip TC_ID reason     # mark TC as skipped with reason (won't revisit)
/negatives --reset TC_ID           # re-open a done case
/negatives --init                  # nuke progress file and rebuild from scratch (destructive)

Every invocation runs auto-sync first — the progress file is always reconciled with the current cases/ directory before any action. Newly added TCs (from Yocto/Linux expansion, new categories, etc.) appear automatically as pending without manual bookkeeping. Removed TCs are flagged as orphaned (not deleted — may be a rename/typo).

---

Progress File

Location: plans/negatives-progress.json

Schema:

{
  "version": 1,
  "generated": "YYYY-MM-DD",
  "cases": [
    {
      "case_id": "dma-002",
      "category": "dma",
      "priority": 1,
      "status": "pending | in-progress | done | skipped | orphaned",
      "started_at": "YYYY-MM-DD" or null,
      "completed_at": "YYYY-MM-DD" or null,
      "notes": "skip reason or oracle warnings" or null
    }
  ]
}