菜单
Verify laboratory experiment changes beyond "tests passed": simulate runs, analysis outputs, trace/provenance checks, and publication-readiness evidence. Use when: "QA this experiment", "verify this harness", "check publishability", "capture evidence", "smoke test this analysis". Trigger: /qa.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Assess and improve codebase readiness for AI coding agents. Dispatches parallel subagents to evaluate style, testing, docs, architecture, CI, observability, security, and dev environment. Produces a scored report with prioritized remediation. Then executes the highest-impact fixes. Use when: "agent readiness", "is this codebase agent-ready", "readiness report", "make this codebase agent-friendly", "agent-ready assessment", "readiness audit", "prepare for agents". Trigger: /agent-readiness, /readiness.
Dialectical premise-and-alternatives audit for a plan, spec, or context packet. Four moves: premise challenge (is this the right problem?), mandatory structurally-distinct alternatives, cross-model outside voice, user-ratified convergence. Operationalizes the AGENTS.md "Diverge Before You Converge" doctrine at the plan-review stage. Use when: about to commit to a plan/spec/design, reviewing a ticket before shape, when "is this the right problem" would be useful, or any time a proposal smells like a symptom fix instead of a root-cause fix. Trigger: /ceo-review, /challenge, /premise-check.
Laboratory CI gate audit and verification workflow. Use when checking whether experiment, harness, analysis, docs, or Spellbook harness changes are safe to ship. Trigger: /ci, /gates.
Parallel multi-agent review for Laboratory changes. Prioritizes correctness, scientific validity, provenance, tests, and harness fit. Trigger: /code-review, /review, /critique.
Take one Laboratory backlog item to merge-ready. Composes /shape, /implement, /code-review, /ci, /refactor, and /qa as needed. Stops before merge. Trigger: /deliver.
Capture and share what changed — every app has a demo path; the format depends on the change and the audience. The spectrum runs from a release-notes blurb ("no demo needed, here's what moved") through a curl + JSON paste, a terminal recording, a screenshot, a GIF, up to a polished narrated launch video. Pick the path that fits the change shape (UI / API / CLI / library / agent tool / internal-only), the audience (PR reviewer / team Slack / external customer), and the time budget. Also scaffolds a project-local demo skill for repos with recurring polished-capture needs. Use when: "make a demo", "generate demo", "record walkthrough", "launch video", "PR evidence", "upload screenshots", "demo artifacts", "make a video", "demo this feature", "create a walkthrough", "show what changed", "paste the output", "release notes blurb", "scaffold demo", "generate demo skill". Trigger: /demo.
| name | qa |
| description | Verify laboratory experiment changes beyond "tests passed": simulate runs, analysis outputs, trace/provenance checks, and publication-readiness evidence. Use when: "QA this experiment", "verify this harness", "check publishability", "capture evidence", "smoke test this analysis". Trigger: /qa. |
| argument-hint | [experiment-path|analysis-path|report-path] |
QA in Laboratory means verifying the scientific workflow surface that changed.
make ci-smoke is necessary, but it is not always sufficient.
| Surface | QA Path |
|---|---|
| Experiment harness | Run deterministic simulate mode, inspect CSV schema, confirm no API keys are required. |
| Live harness path | Check explicit --live, provider preflight, budget cap, model/config logging, and trace output. |
| Analysis script | Run against fixture or committed data; verify output tables/charts match the data source. |
| Publication artifacts | Confirm source data is live, trace-backed, and not mixed with simulated rows. |
| Spellbook harness/docs | Check bridge links, repo brief, skill markers, and make ci-smoke. |
| Website/content | Run content sync/build if the touched files affect the site. |
.spellbook/repo-brief.md, AGENTS.md, and the touched experiment docs.mode or equivalent provenance before accepting
any publishable claim.Blocking rule: simulated rows are harness QA only. If a report, paper, blog post, executive summary, social thread, or data card presents simulated rows as live evidence, QA fails.
Return:
PASS, FAIL, or UNVERIFIED