Results for “witness”

Redige e fundamenta pedido de tutela da EVIDENCIA do CPC 311, que dispensa o perigo de dano. Cobre as 4 hipoteses (abuso do direito de defesa/proposito protelatorio; tese em repetitivo ou sumula vinculante + prova documental; contrato de deposito; peticao instruida com prova documental suficiente sem prova capaz de gerar duvida) e indica quando cabe liminar (incisos II e III, par. unico). Use quando o operador disser tutela da evidencia, art 311, prova documental robusta, tese ja pacificada, abuso de defesa, ou quiser adiantar a tutela sem urgencia.

Runs an adversarial code review with two blind judges analyzing the same code from opposing perspectives to find flaws before production.

Simulates a NeurIPS/SC/ICSE-style peer review with five reviewer personas (HPC, ML, Stats, Reproducibility, Devil's Advocate) that verify every claim against actual result data before submission.

Maneja exibicao de documento ou coisa — contra a PARTE (CPC 396-400: pedido 397, resposta em 5 dias 398, recusa nao admitida 399, presuncao de veracidade se recusa ilegitima 400) ou contra TERCEIRO (CPC 401-404: citacao em 15 dias, audiencia especial 402, deposito/apreensao 403, escusas 404) — e a arguicao de FALSIDADE documental (CPC 430-433: suscitada na contestacao/replica/15 dias da juntada 430, motivos e meios 431, exame pericial 432, coisa julgada se questao principal 433; onus da prova 429). Use quando o operador disser exibicao de documento, obrigar a apresentar documento, incidente de falsidade, documento falso nos autos, parte esconde documento, exibicao de coisa.

Use when sources must stay traceable across sessions and years, when each reference needs a passport recording where it was found, how it was verified, and where it is cited, or when a draft needs a cited-but-unverified sweep before submission.

Internal harness probe for the OI-3 readability-guidance spike. Use only when explicitly told to invoke spike-probe. Verifies that a freshly-created project skill renders into a subagent's context via the Skill tool.

Monta o roteiro da audiencia de instrucao e julgamento — AIJ (CPC 358-368): ordem das provas orais (361 — perito/assistentes, depoimento das partes, testemunhas do autor e do reu), inquiricao de testemunhas (perguntas pelas partes — 459), depoimento pessoal (385-388), pena de confesso, contradita, e as alegacoes finais orais (364) com prazo de 20 minutos. Use quando o operador disser audiencia de instrucao, AIJ, instrucao e julgamento, oitiva de testemunhas, perguntas para a testemunha, depoimento pessoal, alegacoes finais orais, ou houver AIJ designada para preparar.

Validates observable behavior of apps, CLIs, APIs, and generated artifacts against a prewritten contract without inspecting source code.

Derives a comprehensive test plan and writes unit, integration, and end-to-end test cases from user stories and acceptance criteria, flagging issues in prior artifacts and declaring UAT readiness.

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.

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

Adversarial one-question-at-a-time questioning to verify deep reading comprehension of alignment pages, specs, or any document

Screenshot-obsessed, fantasy-allergic QA specialist - Default to finding 3-5 issues, requires visual proof for everything

Incident Post-Mortem Builder

Use to prove that a support process, policy or script change actually took effect — when, for whom, and whether behaviour followed — rather than that it was approved. Trigger for "prove we made that change", "when did this policy actually change", "did the team adopt the new process", evidencing remediation, "we told everyone" claims, or a change that was signed off and never landed.

Monitor running experiments, check progress, collect results. Use when user says "check results", "is it done", "monitor", or wants experiment output.

Resolves legacy references to the pr-review-expert capability by routing to the current runtime agent or skill.

Simulates man-in-the-middle attacks using Ettercap, mitmproxy, and Bettercap in authorized environments to intercept, analyze, and modify network traffic for testing encryption enforcement, certificate validation, and detection capabilities.

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

Approach an app, tool, codebase, website, or product as a genuine first-time user with zero insider context — try it out using only the information provided, get confused where a real newcomer would, and surface the "obvious" questions that people who built or use the thing daily can no longer see. Use this whenever the user wants a first-time-user test, a fresh perspective, a naive walkthrough, a cold read of their README/onboarding/docs/UI, or says things like "pretend you've never seen this", "would a new user get this?", "test my app like a beginner", "what would confuse someone new?", or "give me fresh eyes on this". Also use it when someone wants to find gaps in onboarding, docs, or first-run experience — even if they don't say "fresh eyes" explicitly.

Write legal memoranda with analysis and conclusions. TRIGGERS - Use when user needs help with legal-memo related tasks.

Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.