Results for “acceptance-criteria”

Generates structured Given/When/Then acceptance criteria for a user story or feature slice. Use when translating product requirements into testable scenarios that cover the happy path, edge cases, error states, and non-functional expectations for engineering handoff and QA.

Prepare implementation handoffs with states, flows, assets, edge cases, and acceptance criteria.

Creates structured specifications before writing code to clarify requirements, surface assumptions, and define success criteria, reducing rework and miscommunication.

Translate a vague request or GitHub issue into a concrete, testable spec using five structured elements (problem, scope, acceptance criteria, edge cases, success criterion) before writing any code. Prevents scope creep, PR churn, and mid-implementation pivots.

Acceptance Eval

Load this skill when the user says "close issue", "close-issue", or "/close-issue". Verifies IT and UC acceptance criteria for a story issue, ticks off passing checkboxes, and closes the issue only if all criteria pass and the linked PR has been merged.

Provides a one-page onboarding template for new employees, including a welcome hero, first-week schedule, manager and buddy cards, learning track, equipment checklist, and completion criteria.

Draft a clear, complete, ready-to-send offer letter with compensation, terms, and contingencies — flagging every unconfirmed figure.

UAT Sign-off

Create patient intake forms with history and screening. TRIGGERS - Use when user needs help with intake-form related tasks.

Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.

Create patient intake forms with history and screening. TRIGGERS - Use when user needs help with intake-form related tasks.

Deterministically score, route, rank, and select at most one fully vetted Pleasur.ai Stage 01 blog-keyword candidate using product-fit-dominant business value, traffic opportunity, brand fit, DR-relative winnability, and a free-seeker penalty. Use only after BID and AIO evaluation are complete.

Extract warm prospects from competitor and industry post engagers across LinkedIn, Twitter, and blogs

Check post-launch adoption for a published ORD package and recommend iterate, graduate, or archive

Use only for developer-facing products; plan adoption loops, examples, templates, community, and proof artifacts

当需要评估一个商业想法或服务方向是否适合自己时，特别是面临“选择一个利基市场”的传统建议压力时

Acceptance-test newly added features using browser automation, happy-path flows, screenshots, UX notes, and a written report.

Validate Pleasur.ai Stage 01 blog-keyword candidates with the Business potential, Intent, and Difficulty method using current Ahrefs evidence. Use before AIO vetting and prioritization to reject poor business fits, mismatched search intent, and SERPs the brand cannot realistically win.

Mental models and decision frameworks for building autonomous agents that continuously learn, explore, and accumulate skills in open-ended environments without human supervision

Guides technical evaluation of code review feedback, emphasizing verification before implementation and reasoned pushback over performative agreement.

Imported skill approval from langchain

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.

Guides technical evaluation of code review feedback, emphasizing verification before implementation and reasoned pushback over performative agreement.

Write donor appeal letters with stories and impact. TRIGGERS - Use when user needs help with donor-appeal related tasks.

Onboard

Multi-dimensional lead qualification scoring. Evaluates leads against BANT criteria, firmographic fit, behavioral signals, and intent indicators. Outputs qualified/disqualified verdict with detailed reasoning.

Provides a structured protocol for receiving and evaluating code review feedback, emphasizing technical verification over performative agreement.

Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles.

Generates user stories with clear acceptance criteria from product requirements or feature descriptions. Use when breaking down features for sprint planning, writing tickets, or communicating requirements to engineering.