Loading...
Loading...
Found 24 Skills
Plan and (when feasible) implement or execute user acceptance tests (UAT) / end-to-end acceptance scenarios. Converts requirements or user stories into acceptance criteria, test cases, test data, and a sign-off checklist; suggests automation (Playwright/Cypress for web, golden/snapshot tests for CLIs/APIs). Use when validating user-visible behavior for a release, or mapping requirements to acceptance coverage.
Use when validating that implementation meets specification requirements — applies acceptance-driven backpressure with behavioral validation gates that prevent completion claims without passing tests. Triggers: spec-to-code validation, feature completion verification, pre-merge acceptance gate, release readiness check.
Debugging and acceptance of MaaFramework (MaaFW) applications (in development state, with devices online) — addressing node recognition failures, missed click targets (recognition success ≠ effective clicks), ROI calibration and threshold tuning, single-node run verification, stuck flows and controller connection troubleshooting, end-to-end acceptance, and pipeline_override effect validation; triage is conducted across five layers: configuration, recognition, action, flow, and acceptance, producing root cause conclusions and evidence, with fixes handed over to maafw-pipeline / maafw-interface / maafw-custom. Use when debugging or acceptance-testing a MaaFW application with a device attached — node recognition failures, clicks that miss, ROI calibration and threshold tuning, single-node run verification, stuck flows and controller connection issues, end-to-end acceptance, or pipeline_override effect checks; triage by layer (config / recognition / action / flow / acceptance), then hand the fix back to maafw-pipeline / maafw-interface / maafw-custom.
Add acceptance tests under a functional spec in a ***plain spec file. Use when the user wants to add verification criteria for a specific functional spec, or after adding a functional spec that needs testable success criteria.
Review Go implementations against spec acceptance tests. References go-conventions and agent-conduct.
Use when finishing a ticket or pull request and the user asks to validate, demo, or sign off on delivered behavior, including non-user-facing changes. Triggers include "UAT", "verify", "walk me through", "show what changed", "can we merge?", "sign off", "acceptance test", "demo this", "ready to merge", "validate the changes", "show me it works", and similar phrases indicating a need for an acceptance walkthrough or demonstration before merge.
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.
Run all quality checks (tests, lint, typecheck), fix failures, update the changelog, commit, push, and create/update the pull request or merge request.
Implement Terraform Provider resources and data sources using the Plugin Framework. Use when developing CRUD operations, schema design, state management, and acceptance testing for provider resources.
This skill should be used when the user asks to "break down tasks", "create a task list", "plan implementation", "decompose architecture", "create agent tasks", "plan MVP build", "break down feature", "create execution plan", or mentions task breakdown, agent development workflow, or implementation planning. Two-phase workflow for AI agent development with granular, testable tasks.
Supervise and manage an inner Claude Code instance running in tmux. Use this skill when you need to delegate implementation work to an inner Claude while focusing on task planning, progress monitoring, and end-to-end acceptance testing. Ideal for long-running tasks that would otherwise exhaust a single Claude's context window.
Comprehensive BDD testing with Cucumber and Gherkin syntax. Use when writing feature files (.feature), step definitions, hooks, or implementing Behaviour-Driven Development. Covers Gherkin keywords (Feature, Scenario, Given/When/Then, Background, Scenario Outline, Rule), step definition patterns for Ruby/JavaScript/Java/Python, hooks (Before/After/BeforeAll/AfterAll), tags, data tables, doc strings, and best practices. Triggers on cucumber, gherkin, BDD, feature files, step definitions, acceptance testing, executable specifications.