“acceptance”的搜索结果

Use when reviewing whether an OpenSpec change's execution goal, acceptance criteria, and implementation or verification tasks are aligned. This should trigger for requests such as Review this OpenSpec change with ATDD; Check acceptance criteria against tasks; Find acceptance criteria without task coverage; Detect tasks that diverge from the execution goal; Explain what is missing, vague, ambiguous, partial, absent, or divergent in this OpenSpec change. Part of Plinth Toolkit

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

Write acceptance speeches for awards and honors. TRIGGERS - Use when user needs help with acceptance-speech related tasks.

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

Write clear acceptance criteria for features. TRIGGERS - Use when user needs help with acceptance-criteria related tasks.

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

Generate a User Acceptance Testing plan with scenarios and sign-off criteria. Use when the user says "UAT plan", "acceptance testing", "user testing plan", "how do we test this with users", "test scenarios for business validation", "sign-off criteria", "go/no-go for release", "acceptance test cases", "validate with stakeholders" - even if they don't explicitly say "UAT".

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

Use this skill when designing the human-executable UAT test cases that prove a Salesforce feature works for a specific persona — the per-persona scripts with preconditions, data setup, permission setup, ordered steps, and pass/fail evidence that close out an RTM row. Trigger keywords: UAT test case salesforce, user acceptance test script salesforce, manual test salesforce feature, UAT script per persona, UAT precondition data setup, UAT permission set assignment for testing, negative path UAT case. NOT for high-level UAT planning, defect classification, regression strategy, or sign-off (use admin/uat-and-acceptance-criteria). NOT for the Given/When/Then technique used to write the AC the case is derived from (use admin/acceptance-criteria-given-when-then). NOT for Apex test method generation (use agents/test-class-generator). NOT for test data factory patterns (use templates/apex/tests/TestDataFactory.cls). NOT for performance or load testing.

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

Use this skill when authoring INVEST-compliant Salesforce user stories from gathered requirements: shaping the As-A/I-Want/So-That stem, writing Given-When-Then acceptance criteria, sizing complexity (S/M/L/XL), splitting stories that are too large for a sprint, and emitting handoff metadata that names the next downstream agent. Trigger keywords: user story, INVEST, story splitting, story sizing, As-A I-Want So-That, story handoff, recommended_agents, backlog item shape. NOT for requirements elicitation or stakeholder interviews (use admin/requirements-gathering-for-sf). NOT for the Given-When-Then technique itself in depth (use admin/acceptance-criteria-given-when-then). NOT for UAT test case design (use admin/uat-test-case-design). NOT for backlog prioritization (use admin/moscow-prioritization-for-sf-backlog).

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

Write acceptance speeches for awards and honors. TRIGGERS - Use when user needs help with acceptance-speech related tasks.

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

Write clear acceptance criteria for features. TRIGGERS - Use when user needs help with acceptance-criteria related tasks.

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

Audit whether a "current product focus receipt" (Decision/Now/Why-now/Evidence/Not-now/Cut-suspend/First-visible-proof/ Acceptance-gate/Kill-revisit-trigger/Owner/Review-date) and the work order it gates state a real, testable decision and a real agent launch — not planning-placeholder prose that sounds like an assignment but can't be proven. Use when deciding whether to launch an agent chain against a milestone or a stated "focus," when a work order lacks explicit input/output/owner/proof-gate, or when an acceptance gate would only prove a cached UI state instead of daemon truth. NOT for distinguishing roadmap items from energy-driven sidequests (legible-roadmap-with-sidequests), reviewing a PRD/prototype for product-completeness gaps like cold start or pricing (product-reality-reviewer), or accepting already-finished work against a personal acceptance bar (port-daddy-user-surrogate-pm-review).

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

通过指定的Night Watch负责人协调运维人员配置的Team服务器更新，跟进现有更新机制的验证、数据库迁移与恢复结果，直至更新正式验收。

• 将Team更新到官方main分支
• 协调失败或延期更新的后续执行
• 协调数据库迁移与恢复

将大型功能的RFC设计提案拆分为带依赖关系和验收测试的工作单元，组织多个智能体完成调查、实现、测试与审查，再依次合并变更并验证整个系统。

• 将大型设计提案拆成可验证的任务
• 为多个智能体分配带依赖关系的工作
• 审查并依次合并变更分支

独立验证Kanban中由实施人员移交的成果，核对验收条件和测试证据，并记录批准、修改请求或需要人工判断时的升级处理。

• 按验收条件检查成果
• 复查修改后重新提交的成果
• 将可复现的缺陷退回实施人员

Build a narrowly scoped feature or integration using existing repository structures. Define observable acceptance criteria and non-goals, complete the working path across relevant layers, and stop when focused checks confirm the requested outcome.

中文简介正在准备中。当前显示英语简介。

• Building a feature within a clear scope
• Adding integrations using existing structures
• Defining acceptance criteria and non-goals

Evaluate improvements to Archify diagrams using actual outputs and agent work records. Compare accuracy, readability, and total delivery time to investigate layout, connection routing, diagnostics, and authoring guidance, then document what the evidence supports.

中文简介正在准备中。当前显示英语简介。

• Comparing diagram layouts and connection routes
• Investigating repeated diagram repair attempts
• Testing changes to authoring guidance

Implement approved development stories and code changes with Amelia, a senior software engineer persona. Follow a test-first process: write a failing test, make it pass, then improve the code while checking every acceptance criterion.

中文简介正在准备中。当前显示英语简介。

• Implementing an approved development story
• Making code changes with a test-first process
• Checking implementation against acceptance criteria

Review a completed epic, a group of related development tasks, against its plans, code changes, and commits. Produce a retrospective with evidence-backed findings, follow-up actions, and a decision on whether to accept the work.

中文简介正在准备中。当前显示英语简介。

• Reviewing a completed epic
• Checking delivered work against ticket plans
• Recording evidence-backed improvement actions

Run repeatable tests of Cherry Studio’s key workflows with Playwright, which checks application behavior through automated interactions. Collect results on macOS and Windows and produce English reports for release acceptance or development validation.

中文简介正在准备中。当前显示英语简介。

• Checking key workflows before a release
• Validating application behavior on a development branch
• Running regression tests for a specific task

Guide a scoped coding task through specification, implementation, and review. Set acceptance criteria, verification checks, iteration limits, and approval gates, then correct identified gaps until the requirements pass or a stopping condition is reached.

中文简介正在准备中。当前显示英语简介。

• Build a small feature from specification through verification
• Modify a module against explicit acceptance criteria
• Repeat fixes and checks within an iteration limit

Trace forced authentication and relay chains in a CTF sandbox. Identify what triggers authentication, which service accepts the forwarded identity, and what privilege or artifact results, while distinguishing captured authentication from a successfully accepted relay.

中文简介正在准备中。当前显示英语简介。

• Identify what triggers forced authentication
• Find which service accepts relayed authentication
• Connect relay acceptance to resulting privileges

Trace OAuth and OIDC sign-in flows in a CTF sandbox, from redirects through token exchange to application acceptance. Show where tokens become a recognized identity or permission, and preserve the smallest reproducible flow.

中文简介正在准备中。当前显示英语简介。

• Trace sign-in redirects and callback parameters
• Inspect state, nonce, and PKCE validation
• Check how tokens become application identity or permissions

Trace how JWT, JWS, and JWE tokens become accepted identities or privileges in a CTF sandbox. Examine headers, key selection, and claims, the token's attributes, then preserve a minimal reproducible path demonstrating validation confusion.

中文简介正在准备中。当前显示英语简介。

• Inspect token headers and key selection in a CTF sandbox
• Trace how token claims become application permissions
• Build a minimal reproduction of token acceptance confusion

Turn identified threats and business needs into specific, testable security requirements. Define priorities, explain the rationale, and develop security user stories, acceptance criteria, and test cases linked to the risks they address.

中文简介正在准备中。当前显示英语简介。

• Turn threat models into security requirements
• Write security user stories and acceptance criteria
• Develop security test cases

Design and implement interfaces around the intended audience and constraints. Plan visual hierarchy, spacing, and interface states, support different screen sizes and accessibility needs, then check the appearance against agreed acceptance criteria.

中文简介正在准备中。当前显示英语简介。

• Design an interface for a defined audience and constraints
• Implement layouts that adapt to different screen sizes
• Include accessibility in interface implementation

Compare specification requirements with the codebase and create GitHub issues for unmet requirements. Check existing issues for duplicates, then include requirement IDs, implementation guidance, context, and acceptance criteria in each new issue.

中文简介正在准备中。当前显示英语简介。

• Finding requirements missing from an implementation
• Turning unmet requirements into GitHub issues
• Checking for duplicate issues before creating tasks