Results for “completion-claims”

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

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

Use when about to claim work is complete, fixed, or passing, before committing, before reporting a task done, or before telling the evaluator the batch is ready. Requires running the verification command and reading its output in this turn before any success claim; evidence before assertions always.

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

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

Close an approved plan with zero plan-related deferrals: implement every unfinished item, absorb every connected out-of-scope/follow-up/nice-to-have item parked by prior runs, fix. Use when a plan was marked done with work deferred, or the user says "complete everything", "don't defer", "fix out of scope too", "finish.

Enforces code review practices: receiving feedback with technical rigor, requesting reviews via /code-review, and verifying before claiming completion.

Use before claiming work is complete, fixed, or passing, and before committing or opening a PR - run the actual verification command and read its output before making any success claim.

Full autonomous engineering workflow

Final completion discipline including summary generation, plan document updates, and confirmation that all success criteria from the original plan are satisfied.

Use when experiments complete to judge what claims the results support, what they don't, and what evidence is still missing. Codex MCP evaluates results against intended claims and routes to next action (pivot, supplement, or confirm). Use after experiments finish — before writing the paper or running ablations.

Retroactively audit and fill Nyquist validation gaps for a completed phase

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.

Find outdated stats and assertions in an extracted article. For each, check freshness and propose a replacement with a current source.

Speckit Implement Agent

Create punch lists for construction completion inspection. TRIGGERS - Use when user needs help with punch-list related tasks.

Verify the article’s factual, product, citation, and link integrity before visual production.

Find sources for every numerical claim in the draft, add inline hyperlinks, and add internal links to brand-reference articles. Triggered after /draft.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Archive accumulated phase directories from completed milestones

Federal acquisition compliance auditor for the active Theseus workspace, backed by live FAR/DFARS text via the vendored `ecfr` MCP. USE WHEN the user asks to audit FAR/DFARS clause coverage, validate that cited clauses actually exist in eCFR (catch fabricated or typo'd numbers), check whether a cited clause has been amended since the solicitation issued, validate regulatory references (NIST SP, DAFI, MIL-STD), check that every "shall" requirement has a deliverable, find missing compliance artifacts, audit proposal_instruction ↔ evaluation_factor coverage (UCF Section L↔M or non-UCF equivalent — FAR 16 task orders, FOPRs, BPA calls, OTAs), or "are we compliant with the proposal instructions?". Cross-references the workspace's clause / regulatory_reference / requirement / deliverable / compliance_artifact entities against live eCFR and flags gaps with severity. Format-agnostic. DO NOT USE FOR drafting compliant prose (use proposal-generator) or extracting clauses (Theseus pipeline does that automatically).

Create punch lists for construction completion inspection. TRIGGERS - Use when user needs help with punch-list related tasks.

issue-start 가 증거와 리포트를 게시하고 사람이 승인한 작업을 마무리합니다. 기존 증거의 완결성과 게시 상태를 확인하고, 부족하거나 바뀐 경우에만 보강·재게시한 뒤 PR 을 만듭니다. merge 는 하지 않고 issue-merge 로 넘깁니다. `$issue-end`, "이슈 마무리", "작업 종료", "승인한 작업 PR" 요청에 사용합니다.

Verify the accuracy of claims and statements by extracting individual assertions, identifying authoritative sources, cross-referencing evidence, and assigning confidence-scored verdicts. Use when the user requests fact checking or provides relevant inputs for this workflow.

Send a completion request to the OpenAI API

Adversarially verify an implementation against its objective, acceptance criteria, definition of done, and prohibitions using fresh evidence. Use for completion gates, release readiness, or independent verification after implementation and review.

当需要克服拖延、激发最大行动力以完成一项重大挑战或转型时

Load this skill when the user says "verify-implementation", "verify implementation", or "/verify-implementation". Reviews the implementation against the issue requirements and project coding standards, runs automated checks, and produces a gated report before acceptance criteria are ticked off.

Makes completion state obvious at the end of every response using a red/yellow/green status block.

Routes invocations of the vcf alias to the vc-phase-loop skill, ensuring its defaults and completion rules are followed exactly.

Audit milestone completion against original intent before archiving

Enforce immediate execution of any commitment made in a reply. Use this skill before finalizing ANY reply that contains a promise to act — phrases like "אדווח", "אעדכן", "אשלח", "אחזור אליך", "I'll send", "I'll report", "I'll follow up", "I'll update". Prevents the agent from saying it will do something and then not doing it.

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.