Results for “proof-of-concept”

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, ensuring evidence precedes any success claims.

Writes rigorous mathematical proofs for ML/AI theory. Use when asked to prove a theorem, lemma, proposition, or corollary, fill in missing proof steps, formalize a proof sketch, 补全证明, 写证明, 证明某个命题, or determine whether a claimed proof can actually be completed under the stated assumptions.

Throwaway experiments to validate an idea before build.

Mines a codebase for evidence-backed improvement opportunities, forcing two escalation gates to surface breakthrough ideas, and outputs a ranked portfolio with a plan seed without implementing.

Enforces a verification gate before any completion claim, requiring fresh command output as evidence.

Prepare GPT-pro-ready proof planning or diagnosis bundles from a user's idea, packaging claims, sources, givens, and open questions for review without solving gaps locally.

Validate a business idea using the minimalist entrepreneur framework before building anything. Use to test if an idea is worth pursuing through manual validation and customer feedback.

Define a lightweight, disposable Proof of Life probe to test a risky hypothesis cheaply and surface harsh truths before building real product.

Synthesize source-indexed proof-material items into the final proof-usage playbook. Use when Codex needs to cluster proof items by proof shape, de-duplicate across sources, design reusable taxonomy entries, update proof-usage indexes and source maps, or preserve material-ID links from cooked proof entries.

Turns rough ideas into approved, decision-complete plans with validated structure before coding. Use when users ask in any language for planning, architecture, design direction, feasibility, value judgment, or whether a feature is worth doing before implementation. Not for bug fixes or small edits.

Throwaway experiments to validate an idea before build.

Runs throwaway experiments to validate feasibility before building, producing a verdict with evidence.

PUA Loop — guided iterative development with recurring checks, completion evidence, and pause/abort markers. Use only when the user explicitly asks for loop/自动迭代 mode.

Architect code review with DRY, YAGNI, abstraction, and test coverage principle enforcement

Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.

Require fresh evidence before claiming an implementation, fix, build, or test is complete.

Runs throwaway experiments to validate feasibility, compare approaches, and surface unknowns before committing to a real build.

PUA Loop — guided iterative development with recurring checks, completion evidence, and pause/abort markers. Use only when the user explicitly asks for loop/自动迭代 mode.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Reconcile canonical declarative documents under docs/ with verified implementation discoveries after a FULLY_IMPLEMENTED moonspec-verify verdict. Use when an orchestration run must decide whether verified discoveries show the owning canonical document is impossible, unclear, or inconsistent, apply the smallest correct doc update, or escalate ambiguous authority conflicts and deliberate divergences instead of editing.

Coordinate proof runs across three interfaces: exhaust actionable local proof work first, package exact unresolved obligations for a provider-neutral external solver only when justified, and keep the user informed and in control of consequential choices.

Formally verify programs by writing Lean 4 proofs. Trigger this skill whenever the user wants to formally verify code, generate Lean 4 proofs, prove properties about algorithms or smart contracts, verify invariants, convert program logic into formal specifications, or anything involving Lean 4 and formal verification. Also trigger when the user mentions "qedgen", "lean proof", "formal proof", "verify my code", "prove correctness", "formal verification", or wants mathematical guarantees about their implementation.

Performs a static-analysis penetration test to find exploitable vulnerabilities, providing proof-of-concept payloads and fixes. Covers injection, XSS, authentication bypass, authorization flaws, path traversal, command injection, CSRF, SSRF, hardcoded secrets, and insecure deserialization, with a full attack surface.