36 tagged acceptance testing, measured the same way as everything else here.
Browse within: ai-development 23atdd 23bdd 23agentic-skills 5ai-governance 5
majiayu000/claude-skill-registry
Skill Claude CodeCodex
Build a specification-first Digital FTE that orchestrates accumulated intelligence from Lessons 1-7. Learn to compose execution skills into production-ready agents, validate against specifications, and position for monetization.
Skill Claude CodeCodex
Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers — "/engineer.fix", "a bug came in", "this is broken", "a user reported X", "there's a defect", "we have a regression", "this needs a fix", "another report", "more issues", "still failing", "validation…
Skill Claude CodeCodex
Use at the start of a work session, or any time the question is "what should I pick up now" across the whole project. Triggers — "/engineer.next", "what's next", "what should I work on", "what should I do next", "where do I pick up".
Skill Claude CodeCodex
Use to add a third validation layer to the ATDD workflow — after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies the tests actually catch bugs. Triggers — "/mutate", "/kill-mutants", "run mutation testing", "mutate my code", "kill mutants", "check test quality", "find surviving…
Skill Claude CodeCodex
Use for creating, changing, reviewing, reverse-engineering or accepting requirements, PRDs, prototypes, competitor material or existing systems, including any small UI, field, column, tab, dropdown or legacy-HTML change. Supports /ads, /dig, /prd and /proto intent shortcuts where the host routes them. Always invoke…
majiayu000/claude-skill-registry-data
Skill Claude CodeCodex
Build a specification-first Digital FTE that orchestrates accumulated intelligence from Lessons 1-7. Learn to compose execution skills into production-ready agents, validate against specifications, and position for monetization.
Skill Claude CodeCodex
Use this skill whenever working in a Sima Atlas codebase (any repo containing an atlas/ directory with graph.json and blocks/ / subdirectories). It tells you the standard read order, MCP tool selection, skip-list, write protocol, and stop-signals so you don't burn tokens on irrelevant files. Activate before reading…
Skill Claude CodeCodex
Execute the repository's TESTSE2E.md plan as a complete, autonomous end-to-end integration test — every phase sequentially, failures investigated and fixed immediately, everything logged to a timestamped protocol file. Use when the user asks for an e2e test, a full integration run, acceptance testing, stack…
Skill Claude CodeCodex
Analyze the current repository and generate (or update) its test plans — TESTSE2E.md for autonomous integration runs and TESTSMANUAL.md for guided hand-testing — at the repo root. Use whenever the user wants to set up e2e or manual testing, create or refresh a test plan, "init the tests", bootstrap acceptance testing…
Skill Claude CodeCodex
Conduct the repository's TESTSMANUAL.md plan as a guided manual test — the USER runs every command and GUI action while Claude presents one step at a time, evaluates reported results, proposes (never applies unasked) fixes, and keeps the protocol file. Use when the user wants to test by hand, run commands themselves…
Gesondian/ai-collab-governance-skills
Skill Claude CodeCodex
Use when an AI delivery conclusion depends on partial, indirect, inherited, mock, local, visual, or otherwise limited evidence.
Gesondian/ai-collab-governance-skills
Skill Claude CodeCodex
Use when repeated delivery failures, disputed acceptance, weak evidence patterns, owner-routing mistakes, or trial observations may need reusable governance improvement.
Gesondian/ai-collab-governance-skills
Skill Claude CodeCodex
Use when an AI must decide whether a failure belongs to a feature owner, shared capability owner, data owner, environment owner, or verifier.
wgwtest/project-engineering-strategy
Skill Claude CodeCodex
Use when a software project needs durable cross-session governance for formal documents, WBS or tracker coordination, worktree delivery boundaries, evidence and acceptance states, handoffs, or architecture and design-document control.