「independent review」の検索結果

Review changed user-interface or CLI presentation behavior for accessibility failures. Use for an independent accessibility perspective on a defined change set.

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

Review a change for security defects such as secret exposure, injection, authentication/authorization failures, unsafe deserialization, and dependency risk. Use for an independent security perspective on a defined change set.

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

Review a change for material performance regressions or unbounded resource behavior. Use for an independent performance perspective on a defined change set.

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

Use when SAM Stage 5 Execution has completed and task results need independent verification against acceptance criteria. Dispatches a separate reviewer agent to fact-check implementation outputs and returns COMPLETE or NEEDS_WORK with specific findings and remediation tasks.

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

Provides a pre-submission manuscript audit covering argument, numerical consistency, references and DOIs, writing, figures, CONSORT flow, pre-registration, and the replication archive. Use before paper submission or when a draft needs an adversarial, quote-grounded review with a journal-readiness checklist. Add `--codex` to run the specification independently on Claude and Codex, GPT-6 Astra, and cross-check findings.

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

Run a pre-submission manuscript audit covering argument, numerics, references, writing, figures, methods, preregistration, and replication readiness. Add --codex for a cross-model pass in which Codex and Claude review independently and verify each other's findings.

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

Launch, start, monitor, and collect independent Codex subagents (gpt-6-luna at high, xhigh or max; gpt-6.1-sol for small review batches) for bounded parallel work, from Codex or from Claude Code, including requests supplied as a Markdown file of session prompts. This skill owns Codex subagent transport even when another investigation or review skill defines the questions. Use whenever the user asks for Luna or Sol agents, a swarm, many sessions, a concurrency test, a particular reasoning effort, a Codex subagent from Claude Code, or later collection of reports. Distinguish launch-only requests from requests to wait, collect, or synthesise. Route high and xhigh through the direct launcher; for 16 or more sessions, also invoke the direct launcher instead of native spawn_agent.

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

Builds, revises, restyles, and critiques deliberate, editable Feishu / Lark whiteboards from content, references, existing SVGs, or live boards. Use for whiteboards, infographics, diagrams, system maps, timelines, decision boards, posters, and visual explainers that need factual fidelity, strong hierarchy, intentional composition, and evidence-based review rather than a generic grid of equal cards. Routes creation, revision, and critique through separate playbooks; commits to a content-and-design contract before drawing; validates deterministic SVG defects; renders and inspects the actual artifact; and uses an independent final reviewer for material deliveries.

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

Run the open-pr e2e fixture through a real review in a fresh subagent, grade it against e2e/checklist.md with a second independent subagent, diagnose each failure to the prompt file that owns it, fix, and repeat until clean or the round budget runs out. Use when changing anything under src/ and you want evidence the review still behaves, not just green unit tests.

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

Repair one independently verified Proto UI maintenance finding when governing authority or an explicit product decision fixes the expected result. Use for the bounded remediation and its evidence packet before independent review.

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

Measure the active Agent model with pinned offline ModelTrace sampling and return an unsigned closed-set attribution record. Use before Agent-originated commits, Issue/PR creation or material updates, comments, reviews, and current collaboration writes in either execution mode. Do not treat a fingerprint, declared model label, or record reference as authenticated identity, permission, independent review, or acceptance.

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

Independently review one Proto UI autonomous-maintenance remediation in a fresh read-only context. Use after pui-remediate produces a packet and actual diff. Classify technical-completion eligibility without making product or integration decisions.

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

Verify a change before committing: security, tests, independent review.

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

Choose responsibility for substantial work before deep execution: keep one responsibility's coupled parts in a single lane, and hand a bounded or independent lane to a worker when clean context, an unknown cause, independent review, or coordinator attention materially improves the outcome.

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

Use after meaningful implementation work to create an independent Yardlet review task

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

Implement and finalize one ready rolling-wave slice in one invocation while preserving the lifecycle boundary between implementation and independent review. Use when the user wants a slice delivered end to end without manually invoking implement-slice and finalize-slice, wants main-local implementation by default with workers only when delegation pays, followed by mandatory fresh-context finalization, or says deliver, implement and finalize, or take the slice through review.

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

Validate trained models and analytical claims against their intended decision, independent evidence, and human-reviewed ground truth. Use when reviewing model performance, analysis conclusions, launch claims, or evaluation reports; use failure diagnosis instead when the main task is locating a known defect.

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

Pursue an agreed goal to a working outcome without waiting: decompose it, re-prioritise as evidence arrives, branch, gate, get an independent review (a different model or a fresh reviewer subagent — the writer never approves), merge, prune, and bank the operator's decisions in STATUS.md instead of blocking on them. Trigger on "get it done", "don't wait for me", "proceed autonomously", or when an epic or roadmap objective is handed over. Not a close-out: this work set is expected to grow.

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

Run a two-agent independent review/redteam followed by peer collaboration to produce a consensus superset of findings and enumerated revision requests. Use when Codex 5.5 and Claude Opus 4.7 should first critique a matter independently, then exchange work, synthesize the best combined analysis, and finish with a single agreed revision list.

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

Orchestrate concurrent analysis or implementation across independent domains. Use when a task can be decomposed into independent workstreams (e.g., via simultaneous tool calls or background processes) — spec writing, code review, security audit, feature implementation.

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

Use when executing implementation plans with independent tasks in the current session — trigger phrases "execute the plan", "independent tasks", "parallel tasks", "subagents for the plan","split the plan into subagents". Dispatches a fresh subagent per task with two-stage review after each: spec compliance first, then code quality.

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

Validate CTO Build Framework governance artifacts and file version-bound evidence (runs, reviews, evidence packets) without inflating claims. Use for independent re-execution, internal-consistency reviews, and verdict filing.

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

Independent quality assurance for one SDD Composy task in qa_required: CA coverage, unit/integration/E2E, accessibility, responsiveness, environment, and evidence inventory, producing the QA report and requesting evidence_required. Use when a task finished execution — 'rodar o QA da task', 'testar a TASK-003', 'validar a implementação'. Do NOT use for code review (sdd-review), the final verdict (sdd-verify), or test runs outside an SDD task.

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

Pre-commit verification pipeline — static security scan, baseline-aware quality gates, independent reviewer subagent, and auto-fix loop. Use after code changes and before committing, pushing, or opening a PR.

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