“acceptance”的搜索结果

Check the working conditions of a Japanese job offer item by item against the conditions an employer states in writing, compare the offer letter or 労働条件通知書 with the job posting and what was said in interviews, and separate what is confirmed in writing from what is still only verbal. Use when a user has received an offer, a working-conditions notice, or an employment contract and wants to know what is missing, what conflicts with earlier statements, and what to confirm before the acceptance deadline; do not use to rule on whether the terms are lawful, to decide whether to accept or decline, or to contact the employer on the user's behalf.

中文简介正在准备中。当前显示原文说明。

Prepare a request to change the terms of a Japanese job offer before accepting it, sorting what the user wants changed (pay components, start date, work style, location, title, probation) by priority, tying each ask to a basis the user can show (the written offer, the job posting, what was said in interviews, their own records), working the timing back from the acceptance deadline, and drafting the message to the employer or recruiting agent. Use when a user has an offer and wants to ask for higher pay, a later start date, more remote days, or other changed terms, or wants to know how to raise it without losing the offer; do not use to predict whether the request will succeed, to set a target figure from market rates, to fabricate a competing offer, to decide whether to accept, or to send anything to the employer.

中文简介正在准备中。当前显示原文说明。

ATAC-seq library quality control -- TSS enrichment, FRiP, fragment-size periodicity, library complexity (NRF/PBC1/PBC2), mitochondrial fraction, and ENCODE 4 thresholds. Use when assessing whether an ATAC-seq library passes ENCODE acceptance criteria, diagnosing transposition artefacts, comparing Omni-ATAC vs standard prep quality, or selecting which replicates to drop before peak calling.

中文简介正在准备中。当前显示原文说明。

Discover, build, verify, and optionally export (HTML, optional PDF) the evidence manifest of one SDD Composy task in evidence_required, routing it toward review_required. Use when acceptance evidence must be assembled or checked — 'juntar as evidências da task', 'gerar o relatório de evidências', 'verify the evidence manifest'. Do NOT use to run tests (sdd-qa), review code (sdd-review), or inspect the trace (sdd-trace).

中文简介正在准备中。当前显示原文说明。

Assess requirement clarity, testability, completeness, consistency, and traceability without inventing missing acceptance criteria.

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

任務卡的必要調整。Use when ATM task cards contain proposal-style notes or dated additive acceptance sections such as 識別/行為/狀態機提案、不重啟驗收、ATM 演進規劃書 v2、連鎖影響、治理補丁, and those notes must be re-analyzed into the formal task-card sections.

中文简介正在准备中。当前显示原文说明。

BROWSER VFX ACCEPTANCE SKILL — Use built-in browser/headless browser to automatically verify Cocos VFX block effects and composed VFX recipes in BattleScene preview (`http://localhost:7456`, `previewMode=true`, `previewTarget=5`). USE FOR: VFX health audit, per-block smoke validation, combo recipe regression checks before merging `vfx-block-registry.ts` / `vfx-effects.json`. DO NOT USE FOR: Cocos Editor window screenshot capture, compile-error debugging, or pure log-only diagnosis without browser preview.

中文简介正在准备中。当前显示原文说明。

Run a structured discovery interview and produce a complete, developer-ready Product Requirements Document. Load when the user asks to write a PRD, create product requirements, document a feature, define user stories with acceptance criteria, or turn a rough idea into a formal product requirements document. Also triggers on "document this feature", "write requirements for", "create a one-pager", "turn this into a PRD", "I need a PRD for", or any request to produce a structured product document for stakeholder alignment or engineering handoff. Supports Full PRD, Lean PRD, and One-Pager formats. Note: for executable feature specifications (FRs, NFRs, ACs as Given/When/Then consumable by AI coding agents), route to `feature-spec` instead — PRDs frame the product, feature-specs encode the implementable contract.

中文简介正在准备中。当前显示原文说明。

Write the executable feature specification — the WHAT and WHY artifact that agents and reviewers treat as source of truth. Owns both /specify and /clarify modes. Load when the user asks to write a feature spec, write a specification, write an executable spec, define functional requirements, capture acceptance criteria as Given/When/Then, or when the spec-driven-development orchestrator routes here. Also triggers on "feature spec", "executable spec", "/specify", "/clarify", "write the spec for this feature", "specification for", "spec-driven", "machine-readable spec". Output: docs/specs/YYYY-MM-DD-<slug>-feature-spec.md. Hard gate: cannot Approve while [NEEDS CLARIFICATION] markers remain.

中文简介正在准备中。当前显示原文说明。

ATAC-seq library quality control -- TSS enrichment, FRiP, fragment-size periodicity, library complexity (NRF/PBC1/PBC2), mitochondrial fraction, and ENCODE 4 thresholds. Use when assessing whether an ATAC-seq library passes ENCODE acceptance criteria, diagnosing transposition artefacts, comparing Omni-ATAC vs standard prep quality, or selecting which replicates to drop before peak calling.

中文简介正在准备中。当前显示原文说明。

Use this skill to understand when electronic records are acceptable to FMCSA inspectors. Covers PDF, original-format, and search-ability requirements.

中文简介正在准备中。当前显示原文说明。

Synthesizes evidence-linked feedback from validation results, confidence evidence, and iteration triggers. Proposes bounded revision guidance for a stated acceptance failure. Activate on 'synthesize feedback', 'improvement suggestions', 'actionable feedback', 'iteration guidance', 'feedback generation'. NOT for iteration detection (use dag-iteration-detector) or convergence tracking (use dag-convergence-monitor).

中文简介正在准备中。当前显示原文说明。

Records and evaluates event-specific probability forecasts for agent outputs. NOT for validation or automatic acceptance.

中文简介正在准备中。当前显示原文说明。

Discipline an AI agent needs to work an issue/task tracker (Jira, Linear, GitHub Issues) as the shared source of truth: pull the right next item instead of inventing work, search before creating to avoid duplicates, write actionable items with checkable acceptance criteria, keep status transitions honest, and link work to items via branches/PRs/commits so progress is legible. Use when an agent picks up tracker work, files a new issue, updates status, or closes an item. NOT for authoring the PR itself (use agent-pr-authoring), roadmap-level planning and prioritization (use legible-roadmap-with-sidequests), or the mechanics of multiple agents coordinating on the same codebase (use multi-agent-coordination).

中文简介正在准备中。当前显示原文说明。

Codex Plan Mode 専用。docs/PLAN/{YYMMDD}_{slug}/ に schema v3 仕様書を作成する。 Gate 契約 (Goal / Constraints / Acceptance Criteria)、Mermaid 図、Cursor Agent 委任ヒントを含む。 Trigger: spec-codex

中文简介正在准备中。当前显示原文说明。

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

中文简介正在准备中。当前显示原文说明。

Closes a finished story: verifies each acceptance criterion, checks for design or ADR deviations and updates its status. Use when the user says a story is done, finished or ready to close.

中文简介正在准备中。当前显示原文说明。

Breaks one epic into implementable stories with acceptance criteria. Use when the user wants stories for an epic or the next batch of work to build. Not for turning the whole design into epics.

中文简介正在准备中。当前显示原文说明。

Align explicit requirements, implicit expectations, non-goals, observable acceptance, evidence, and decision authority before OpenSpec specs and executable tasks finalize. Use when authoring or updating a proposal, design, specs, or tasks, or when a request hides a material product choice. Do not use for routine implementation of an already-authorized task, unrelated conversation, or facts the repository can answer.

中文简介正在准备中。当前显示原文说明。

Use when a Spark change needs its authoritative owner, affected boundaries, risks, acceptance criteria, and smallest verifiable slice established before implementation or review.

中文简介正在准备中。当前显示原文说明。

受け入れ基準書を作成する。検収基準、完了条件の定義時に使う。

中文简介正在准备中。当前显示原文说明。

将抽象的Acceptance Criteria（Given-When-Then）转换为具体的数值示例和真实对话，让AC对PM/客户/测试人员更易懂。适合在AC编写完成后、准备测试或向客户展示时使用，当AC格式正确但过于抽象时。帮助不熟悉BDD的PM/BA/测试人员理解测试场景，让AC从抽象规则变成可直接用于手动测试的具体步骤。

中文简介正在准备中。当前显示原文说明。

Turn vague Acceptance Criteria into measurable checks and test assertions

中文简介正在准备中。当前显示原文说明。