Results for “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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

Coordinate updates to an operator-configured Team server through its designated Night Watch owner. Use the existing deployment controller’s validation, recovery, and acceptance records to follow the requested update through completion.

• Updating a Team server to official main
• Following up on failed or deferred updates
• Coordinating database migration and recovery

Break an RFC, a written design proposal, into work units with dependencies and acceptance tests for multiple agents. Organize research, implementation, testing, review, queued merges, and final system verification for features too large for one pass.

• Splitting a large design proposal into verifiable work units
• Assigning dependent tasks to multiple agents
• Managing review and queued merges of agent-built branches

Independently reviews deliverables handed over through Kanban, checks them against acceptance criteria and test evidence, and records an approval, actionable change request, or escalation when a human decision or external prerequisite is needed.

• Reviewing deliverables against acceptance criteria
• Rechecking corrections after a change request
• Returning reproducible defects to the implementer

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

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

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

Create structured Markdown specifications that AI agents can read and use. Organize requirements, constraints, interfaces, acceptance criteria, and testing plans into a self-contained document with clear definitions and examples.

• Writing specifications for AI-assisted implementation
• Defining requirements and acceptance criteria
• Documenting APIs and data contracts