「evidence」の検索結果

Submit compact CIViC GraphQL requests for cancer variant interpretation schema inspection and targeted evidence retrieval. Use when a user wants concise CIViC summaries

日本語の概要は準備中です。原文の説明を表示しています。

Build polished analytical reports for executive, product, business, or technical audiences. Use when the task needs a durable answer-first narrative with evidence-backed findings, visuals or tables, caveats, and source context.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze product or business data to support a decision or recommendation. Use when a decision depends on metric-backed evidence, such as choosing a direction, prioritizing an opportunity, evaluating a change, segmenting users, sizing tradeoffs, or deciding what to do next.

日本語の概要は準備中です。原文の説明を表示しています。

Develop evidence-backed structural and architectural security hardening proposals from vulnerability disclosures, supplied findings, incident or assessment documents, source code, or a completed Codex Security scan. Use when a user asks for systemic improvements, alternatives beyond per-finding patches, before-and-after security architecture views, engineering tradeoff analysis, or an implementation-ready plan for a selected hardening option. Also use automatically after a Codex Security scan with reportable findings when the top-level scan workflow requests final-report hardening guidance.

日本語の概要は準備中です。原文の説明を表示しています。

Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate, edit, apply, push, or merge the patch.

日本語の概要は準備中です。原文の説明を表示しています。

Triage supplied or imported security findings against a repository using its security policy and static code evidence. Accepts scanner reports, advisories, GitHub findings, and Jira or Linear tickets. Do not use for discovery, duplicate triage, runtime validation, or fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Capture and inspect iOS leaks and memgraphs. Use when debugging leaked objects, retain cycles, memory growth, or before/after leak evidence.

日本語の概要は準備中です。原文の説明を表示しています。

Build an evidence-cited SWOT of one company — yours or a competitor's — from public sources, ending with the S-O/W-T crossings. Use for strategy reviews, board prep, or competitor depth.

日本語の概要は準備中です。原文の説明を表示しています。

Mine public reviews, app stores, and forums for unmet needs, competitor weaknesses, and switching triggers — with quoted evidence. Use when you want customer voice without waiting on interviews.

日本語の概要は準備中です。原文の説明を表示しています。

Research and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.

日本語の概要は準備中です。原文の説明を表示しています。

Scheduled delta monitoring against a prior competitive snapshot. Use when tracking competitors on a cadence: material shifts only, cited evidence, battle-card update flags, runs unattended.

日本語の概要は準備中です。原文の説明を表示しています。

Map a market's segments, players, substitutes, and whitespace with cited evidence. Use when entering or re-evaluating a market before sizing, positioning, or picking competitors to study.

日本語の概要は準備中です。原文の説明を表示しています。

Map evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing. Use when the question is where the next tranche of growth comes from, and at what risk.

日本語の概要は準備中です。原文の説明を表示しています。

Feature planning and implementation with 4 adaptive phases (Specify, Design, Tasks, Execute). Auto-sizes depth by complexity. Writes testable requirements in EARS notation, atomic tasks, atomic Conventional Commits, and requirement traceability. Ships deterministic Python validation scripts so structural gates are enforced by code, not memory. Features an independent Verifier (author != verifier, evidence-or-zero), a discrimination sensor, a decision log (STATE.md), a test-coverage matrix, and a self-improving lessons layer. Stack-agnostic and tool-agnostic. Use when (1) planning features, (2) implementing with verification and atomic commits, (3) validating an implementation against a spec. Triggers on "specify feature", "discuss feature", "design", "tasks", "implement", "validate", "verify work", "UAT", "record decision", "pause work", "resume work". Do NOT use for pure architecture decomposition analysis or standalone technical design documents.

日本語の概要は準備中です。原文の説明を表示しています。

Use when challenging ideas, plans, decisions, or proposals. Invoke to play devil's advocate, run a pre-mortem, red team, stress test assumptions, audit evidence quality, or find blind spots before committing. Do NOT use for building plans, making decisions, or generating solutions — this skill only challenges and critiques. For a multi-agent panel that challenges and then commits to a verdict, use the-jury.

日本語の概要は準備中です。原文の説明を表示しています。

Turn bounded draft, publication, and comment evidence into a concise WeChat Official Account operating review and next-step plan.

日本語の概要は準備中です。原文の説明を表示しています。

frame proof, HTML frames, screenshots, recording, PR proof, e2e evidence, validate visually. Daytona artifacts workflow for validated screenshots and optional videos.

日本語の概要は準備中です。原文の説明を表示しています。

create a fraimz, make fraimz, prove it works, frame proof, PR proof, validate experience, e2e evidence, fraimz.html. The full fraimz loop — frame the claim, drive the real app via CDP, validate/repair, output fraimz.html. Use whenever a task ends with "please create a fraimz" or any change needs end-to-end proof.

日本語の概要は準備中です。原文の説明を表示しています。

Use with any iPolloWork template generating video, slides, websites or other designs from iPolloWork reference documents and a creative-context.json attachment. Read unified content, design evidence and asset paths; apply the edited brief and verify actual asset reuse. Does not parse documents with models.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose failing GitHub Actions runs from bounded run, job, and step evidence, propose a focused fix, and modify the local checkout only when the requested task includes implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Assess release health from Sentry errors, regressions, affected users, crash evidence, and comparison with the previous stable release.

日本語の概要は準備中です。原文の説明を表示しています。

Turn project evidence into maintainable Notion briefs, decision records, runbooks, and status documents without overwriting unrelated content.

日本語の概要は準備中です。原文の説明を表示しています。

Triage Linear issues using bounded searches, duplicate checks, explicit team and project scope, and evidence-backed priority recommendations.

日本語の概要は準備中です。原文の説明を表示しています。

Reconcile bounded Stripe payment and payout records with supplied business records while preserving object IDs, currency, time zone, and discrepancy evidence.

日本語の概要は準備中です。原文の説明を表示しています。