Results for “completion-claims”

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

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.

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.

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

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.

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

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).

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" 요청에 사용합니다.

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.

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

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

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.

Read-only query methods for PumpFun claims — unclaimed token rewards, creator vault balances, volume accumulators, distributable fees, and current-day token previews across Pump and PumpAMM programs.

Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission. Codex designs ablations from a reviewer's perspective, CC reviews feasibility and implements.

Plan structure validation, phase completeness checks, reference integrity verification, and artifact existence confirmation. Provides the structured verification layer ensuring GSD artifacts are well-formed and complete.

Drafts litigation-ready U.S. pre-suit demand letters that function as settlement instruments and defensible future exhibits. Enforces element-driven narratives, verified authority, damages methodology, and ethics guardrails. Use this skill when the user mentions demand letter, pre-suit demand, breach and cure notice, settlement demand, insurance policy-limits demand, Stowers demand, FDCPA collection letter, notice of intent to file, cease and desist demand for payment, or pre-litigation correspondence. Also trigger when the user asks about FRE 408 framing, contractual notice compliance, statutory pre-suit prerequisites, evidence preservation notices, or quantifying damages for a demand package. Skill includes 14 verified real-letter exemplars referenced from `references/ARCHETYPE-INDEX.md`.

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

Clade coverage-driven project review — walks every VERIFY.md checkpoint, fixes failures in-session, converges when all checkpoints pass. NOT the Claude Code built-in /review (which reviews a single pull request diff) — if the user wants a PR review, route to /review-pr (Clade's PR reviewer) or the CC built-in.