Skip to content

wanshuiyin/Auto-claude-code-research-in-sleep / skills/skills-codex/proof-orchestrator

proof-orchestrator

Verified

Manage a stateful, run-directory-based proof project with Codex: continuation across runs, run-local source bookkeeping, manual GPT Pro handoff packages when a local attempt stalls, and an optional DeepSeek second opinion as additional evidence only. Use when the user asks for proof-run orchestration, a GPT Pro handoff, or cross-run proof continuation — use /proof-writer for ordinary proof drafting and /proof-checker for rigorous verification or submission acceptance.

references/deepseek-routing.md

View on GitHub
# DeepSeek Reviewer Routing

Use DeepSeek only after the user explicitly requests the optional adversarial
review branch in `proof-orchestrator`. Codex remains the controller: gather
context, write the brief, call DeepSeek, validate the response, then produce
the final audit.

## Preferred Route: DeepSeek MCP

Prefer an installed MCP bridge that can call DeepSeek directly, such as
`mcp__llm_chat__chat`.

The bridge is generic: `llm-chat` defaults to OpenAI `gpt-6.1-sol` unless the
environment overrides it. When `LLM_FALLBACK_MODEL` is unset, the 504-timeout
fallback inherits the configured `LLM_MODEL` (which may be DeepSeek or another
third-party model), so the fallback is not guaranteed to be a different model
and "the configured default" may not be DeepSeek at all. Before labeling any
output `llm-chat-deepseek`, VERIFY the actual provider/model: the bridge
response reports the model it used — require it to be a DeepSeek model. If the
response comes back from a non-DeepSeek model (wrong default, or the bridge's
timeout fallback), mark the run `DEEPSEEK_REVIEW_BLOCKED` and record what
actually answered; never record a non-DeepSeek or unknown-model response as
DeepSeek evidence or as cross-family review — for Codex this matters doubly,
since a silent GPT fallback would be SAME-family review mislabeled as
cross-family. `unknown` fails closed.

Use the verified DeepSeek model unless the user names another DeepSeek model.
Do not expose or write API keys. If the MCP bridge is missing, unavailable, or
misconfigured, do not create credentials inside the repository; report setup as
blocked or use the fallback route.

## Fallback Route: Local Audit

If the DeepSeek MCP route is unavailable, do not improvise credentials, install
unrequested software, or run an undeclared wrapper. Report the external route
as blocked. A local audit may still identify issues, but it must be labeled
`local-executor-fallback` (or `local-codex-fallback` in the Codex mirror)
and cannot satisfy a cross-family acceptance gate.

## Reviewer Prompt Template

```text
ROLE:
You are an adversarial mathematical proof reviewer. Find false statements,
hidden assumptions, missing side conditions, illegal interchanges, quantifier
errors, and counterexamples. Prefer an honest blocker over a plausible repair.

TASK:
Audit the target proof below. Do not edit source files. Return a structured
proof audit.

OUTPUT FORMAT:
- Verdict: PASS | WARN | FAIL | BLOCKED | NOT_APPLICABLE
- Claim status: PROVABLE AS STATED | PROVABLE AFTER WEAKENING / EXTRA ASSUMPTION | NOT CURRENTLY JUSTIFIED
- Claim restatement
- Obligation ledger
- Issues, each with severity, category, location, claimed step, problem,
  counterexample status, downstream effect, and minimal repair
- Counterexample pass
- Remaining risks

MANDATORY CHECKS:
Use the taxonomy and side-condition checklist from
references/proof-audit-rubric.md.

TARGET PROOF:
<insert exact proof content and source locations>
```

## Response Validation

After DeepSeek returns:

1. Confirm the output follows the requested issue schema.
2. Check that every fatal or critical issue cites an exact source location or a clearly identifiable proof step.
3. Verify any claimed counterexample algebraically before calling it found; otherwise relabel it as a candidate.
4. Preserve DeepSeek's substantive critique, but correct output-format errors and add local source line numbers when available.
5. If the response is empty, truncated, or mostly generic, retry once in a fresh DeepSeek session; if still unusable, mark the audit `ERROR` or `BLOCKED`.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall