acceptance-criteria-gwt

acceptance-criteria-gwt is a skill for Claude Code, Codex from makifbaysal/tasktrooper. It costs 34 tokens per session (1,512 once invoked), scanned A, original, Apache-2.0.

A format for writing acceptance criteria as observable Given, When, Then statements. Acceptance criteria are specific conditions that developers, testers, and reviewers use to decide whether a task is complete.

In plain words
What is it for?
It helps describe normal and failure cases as executable checks, such as what must happen after a user action or command.
Why use it?
It prevents vague requirements that cannot be tested. Keeping the criteria in the task's checklist also lets each person record completion and an independent review result.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps describe normal and failure cases as executable checks, such as what must happen after a user action or command.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/makifbaysal/tasktrooper/acceptance-criteria-gwt
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add makifbaysal/tasktrooper --skill acceptance-criteria-gwt
Clone the repo
git clone --depth 1 https://github.com/makifbaysal/tasktrooper

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for acceptance-criteria-gwt

README.md
[![agentmods](https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/acceptance-criteria-gwt/github.svg)](https://agentmods.dev/skills/makifbaysal/tasktrooper/acceptance-criteria-gwt)
Your own site
<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/acceptance-criteria-gwt"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/acceptance-criteria-gwt/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for acceptance-criteria-gwt

Your own site · 80×15
<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/acceptance-criteria-gwt"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/acceptance-criteria-gwt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,512 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.01512
Opus 5.5 $0.00014 $0.00605
Sonnet 5.5 $0.00007 $0.00302
Haiku 4.5 $0.00003 $0.00151

Measured 8d ago against content hash 783341f7af4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

acceptance-criteria-gwt scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

catalog/agents/product-manager/skills/acceptance-criteria-gwt/SKILL.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Acceptance Criteria (Given/When/Then)

Overview

Acceptance criteria are the contract QA tests the product against and the PM verifies at UAT. If a criterion isn't executable, it can't be verified — and unverifiable criteria are where defects hide.

Core principle: Every criterion is an observable behavior QA can execute with a command or a click path. No aspirational adjectives.

The shape

Given [precondition], When [action], Then [measurable result].

Where they go

Criteria live in the board task's own acceptance_criteria field — an array of strings, one criterion per item, passed to create_board_task (or update_board_task to replace the whole list). Each item becomes a checkbox the implementer ticks with set_criterion_completed, and that QA (in ready_for_qa/in_qa) and you (in pm_uat) then rule on independently with review_criterion. The tick is the implementer's claim — QA and PM never call set_criterion_completed; your verdict is review_criterion.

Never write them into description. A criteria block pasted as markdown leaves the task's checklist empty: nothing to tick, nothing the move guard can check, and the prose copy goes stale the moment the real criteria are edited.

Testability gate

For each criterion, before you save it, write down:

  • who executes it — QA in in_qa, and the PM in pm_uat with browser or mobile tools (or http_request against the task's own preview when the surface is an API, not a screen);
  • the action — a click path, a URL, or a request;
  • the exact observable — text, a count, an element state, or a file.

If the behaviour is user-facing, the Then must be visible in the UI — not a status code standing in for what the user sees. If nobody outside the code can observe it, it belongs in technical_description, not in a criterion.

Declarative When, concrete Then

Write the When as what happens, not the click-by-click path — the cucumber test: "Will this wording need to change if the implementation changes?" If yes, it's too imperative. One behaviour per criterion. Put exact copy strings in quotes in the Then; "an error appears" is not testable, "'Title must be at most 200 characters' appears under the field" is.

Read the full file on GitHub · 112 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 112 lines · 34 tokens per session scan A 783341f7af4f

Subscribe to this mod's changes

acceptance-criteria-gwt is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 1,512 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-05.