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/stress-tests.md

View on GitHub
# External Review Stress Tests

User-operated manual browser handoff is the default for proof-orchestrator
stress tests; Codex never operates a browser.
First complete the local attempt and isolate the exact obligation being tested.

For every test:

1. Create a fresh local run directory.
2. Keep only the required source snapshots under `sources/` and record them in
   `source-manifest.md`.
3. Prepare `browser-prompt.md` as exact copy-ready text and `handoff.md` as the
   user-facing upload/paste instructions.
4. Use a fresh ChatGPT Project for an unrelated test. A direct continuation may
   reuse a Project only when the source set still matches, and must use a new
   conversation.
5. Save the returned text as `gpt-pro-output.md`, then run correctness and
   exposition passes separately.

If a test names PDFs or other primary documents, mark them as required separate
uploads in `source-manifest.md`. Do not silently replace them with extracted
text, memory, or a bundle.

Only when the user explicitly asks Codex to perform the dispatch should Codex
load `call-gpt-pro` and follow its selected-route instructions. A failed browser
route is not authorization to spend API credit.
## DeepSeek Route Tests

- With no explicit DeepSeek request, complete the local pipeline without a
  remote reviewer and without creating `deepseek-review.md`.
- With an explicit DeepSeek second-opinion request and an available llm-chat
  route, save raw output, validate issue locations and counterexamples, and
  integrate only checked findings into `audit.md`.
- With an explicit request but no available route, mark
  `DEEPSEEK_REVIEW_BLOCKED`; label any local audit as a fallback and do not
  claim independent acceptance.
- Never redirect existing paper workflows from `/proof-checker` to this optional
  branch.
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