Results for “verdict”

Composite skill — take a PR from "I think it's ready" to merged with full gate verification. Chains pr-merge-readiness (verdict) → ci-watch / gh-fix-ci (if blockers) → gh-address-comments (if review needed) → ship (when verdict is MERGE). Use as the one-call answer to "can I merge this?" instead of running 4 skills sequentially.

Drafts a Motion for Judgment Notwithstanding the Verdict (JNOV) under FRCP 50(b) or state equivalents, with alternative new-trial request. Builds element-by-element evidentiary insufficiency arguments using transcript citations and preserves the appellate record. Use when drafting JNOV motions, post-trial motions, renewed judgment as a matter of law, or challenging jury verdicts for insufficient evidence.

Read artifacts from the shared bench — the workspace where desks leave findings, verdicts, and work products for each other and the operator.

Triage an incoming commercial document, route it to the right review skill, run a first-pass red-flag scan, and produce a consolidated verdict.

Multi-dimensional lead qualification scoring. Evaluates leads against BANT criteria, firmographic fit, behavioral signals, and intent indicators. Outputs qualified/disqualified verdict with detailed reasoning.

Reviews all uncommitted changes in the current Git repository and produces a structured code review report with findings and a verdict.

Compares two code versions for semantic equivalence by tracing both side-by-side, identifying divergences, and producing a structured verdict.

Gates a git branch before merge by running code review, security, test, and accessibility passes on the diff, then emits a single verdict.

Launches four parallel adversarial review agents covering security, scope, fidelity, and test gaps, then synthesizes findings into a ranked verdict for plans or feature branches.

Reviews code diffs or explicit file sets through independent correctness and QA lenses, producing a severity-ordered verdict for pre-merge audits or review gates.

Scores any US stock ticker through Warren Buffett's four-lens framework (business simplicity, moat, management, valuation) and returns a weighted HOLDABLE/WATCHABLE/AVOID verdict.

Analyse experiment results, run validity checks (SRM, exposure parity, data integrity, novelty/primacy), interpret causally, make a ship/iterate/kill decision against the pre-declared rule, and append to cumulative learnings. Forces honest readouts — strips significance claims from underpowered or peek-violating tests; never lets directional results masquerade as causal wins. Load when results exist, or when the user says "read out this experiment", "analyse the test", "did the test win", "interpret the results", "what did we learn", "ship or kill", or when the experimentation orchestrator routes here.

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.

Compare, cross-review, and merge competing plans from multiple agents into one executable direction with a clear handoff.

Record a decision: finalized → ADR (optionally rule + guide or spec + plan); open proposal → RFC. Use for 'we decided', 'record this decision', 'make it a standard', 'draft an RFC', 'should we switch to Y'. Not for feature planning or documenting existing code.

Give a decisive, project-grounded point of view in the subject's own shape: a graded verdict on an external-adoption question, a holistic take on a document, or a position on a user-supplied approach set. Use for a solo POV, a mid-session second opinion, a named-peer cross-check, any request to consult other models or reconcile their opinions, an `oracle` panel, or a correction-cost-gated proactive cross-check offer. Not for findings review (use ce-doc-review), neutral explainers, or generating options (use ce-ideate or ce-brainstorm).

Decide

Perform a non-destructive post-implementation verification gate validating the implementation against spec.md, plan.md, tasks.md, and constitution.md.

See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio, video), and create real time alerts for events from live streams or desktop capture.

Promove o cumprimento de sentenca (titulo executivo judicial) — disposicoes gerais (CPC 513), titulos judiciais (CPC 515), cumprimento DEFINITIVO de pagar quantia com intimacao em 15 dias e multa de 10% + honorarios de 10% se nao pago (CPC 523 §1, penhora/avaliacao §3), demonstrativo atualizado do debito (CPC 524), cumprimento PROVISORIO sob recurso sem efeito suspensivo (CPC 520-522), alimentos com prisao civil (CPC 528 §3) e Fazenda Publica (CPC 534-535). Use quando o operador disser cumprimento de sentenca, executar a sentenca, intimar para pagar em 15 dias, multa de 10% cumprimento, cobrar sentenca transitada.

Quick feasibility and novelty check — go/no-go decision for this week's build

Validate Pleasur.ai Stage 01 blog-keyword candidates with the Business potential, Intent, and Difficulty method using current Ahrefs evidence. Use before AIO vetting and prioritization to reject poor business fits, mismatched search intent, and SERPs the brand cannot realistically win.

Builds Vue 3 components, composables, and Vite projects using JavaScript with JSDoc type annotations instead of TypeScript.

Pressure-test any business idea with a five-angle adversarial panel (Critic, Champion, Analyst, Investigator, Customer) that returns a single GO/RESHAPE/KILL verdict with the cheapest test to de-risk it.

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

Police the project's vocabulary — bust vague terms, keep the CONTEXT.md glossary sharp, and lock in decisions worth remembering as ADRs. Use when the user debates naming, says "what should we call this", asks to pin down terminology, wants a decision recorded, or when another skill (hot-seat, whiteboard) surfaces a decision that clears the ADR bar. Just reading the glossary for vocabulary is NOT this skill — trigger only when the words or decisions are being changed.

Verify code changes work by running them. Proves through execution, not just inspection.

Scans source code repositories across C++, Android, iOS, and Web to classify files, detect embedded third-party libraries, and produce actionable four-level verdicts per module with interactive HTML reports.

Close the PDCA loop on this session's diff. Headed playwright-cli, fix as you go. Use when "test my changes", "PDCA this". Pixel diffs → test-visual-regression. Story CRUD → test-qa. Monkey / guest vs logged-in → test-exploratory.

Audits source code across C++, Android, iOS, and Web to classify files, detect embedded third-party libraries, and produce four-level verdicts with interactive HTML reports.