test-case-authoring SKILL.md skillA

test-case-authoring from rampstackco/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add rampstackco/claude-skills/test-case-authoring@git:20261116.cf0eea0

Pins git:20261116.cf0eea0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
rampstackco/claude-skills
Path
skills/test-case-authoring/SKILL.md
Versions recorded
2
Latest version
git:20261116.cf0eea0, committed Nov 16, 2026
First version recorded
Nov 8, 2026
Size
11,710 bytes
Repository stars
1,100
License
MIT

Write the test plan and test cases for a single work item: every acceptance criterion traced to a case, each case with test data, steps, an observable expected result, a level, and the evidence a pass must leave behind. Use this skill whenever the user wants to write test cases, a test plan, or QA notes for a ticket, plan regression tests for a bug fix, build a traceability matrix, choose between unit, integration, end-to-end, and manual tests, or charter exploratory testing for a spike.…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Test Case Authoring

Write the tests for one work item so the QA notes on the ticket have real content and the fix verification on a bug names a real test. Tool-agnostic: works with any test runner, any tracker, and any test management tool.

---

## When to use

- A story is ready and its acceptance criteria need test cases
- A bug fix needs a named verification test and a regression set
- QA notes on a ticket say "test it" and nothing else
- Checking whether a set of acceptance criteria is testable at all
- A spike needs an exploratory charter instead of pass/fail cases
- A coding agent will run the tests and needs to know what evidence to return

## When NOT to use

- Site-wide QA sweeps before a launch or after a deploy (use `qa-testing`)
- Writing the acceptance criteria themselves (use `ticket-authoring`, or `pm-spec-writing` for the spec behind them)
- Auditing a whole site for accessibility (use `accessibility-audit`)
- Reviewing the code change (use `code-review-web`)
- Deciding go or no-go for a release (use `release-management`; for a first launch or cutover, use `launch-runbook`)
- Deciding which items deserve testing effort first (use `backlog-triage`)

---
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2h2cmrhh3oyj7xkb/f620568214ff44350638e6c4d4b6d7068de5f5f1e75c0eccc23bf9e77ae6b006.json

Then /plugin install test-case-authoring@markdownregistry-2h2cmrhh3oyj7xkb in Claude Code. It installs git:20261116.cf0eea0, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add rampstackco/claude-skills/test-case-authoring@sha256:f620568214ff4435

The line at the top of this page pins the label git:20261116.cf0eea0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_2h2cmrhh3oyj7xkb.svg)](https://markdownregistry.com/a/art_2h2cmrhh3oyj7xkb)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in rampstackco/claude-skills/test-case-authoring since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of test-case-authoring from somewhere else? Ask it: where did my test-case-authoring come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 2 versions of this file, between Nov 8, 2026 and Nov 16, 2026, about one every 7 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261116.cf0eea0 latest2026-11-16 cf0eea0 11,710 BA view · diff
git:20261108.05905102026-11-08 0590510 11,653 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (11710 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

rampstackco/claude-skills · 1,100 stars · license MIT · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_2h2cmrhh3oyj7xkb
GET https://markdownregistry.com/api/v1/resolve?ref=rampstackco/claude-skills/test-case-authoring
GET https://markdownregistry.com/api/v1/blob/f620568214ff44350638e6c4d4b6d7068de5f5f1e75c0eccc23bf9e77ae6b006

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from rampstackco/claude-skills

rampstack Plugin marketplace
rampstackco/claude-skills · .claude-plugin/marketplace.json · RampStack Claude Skills: the website lifecycle as installable skills. (4 plugins: rampstack-skills, rampstack-starter…
git:20261116.9d281db · audit A · 1,100 stars
accessibility-audit SKILL.md skill
rampstackco/claude-skills · skills/accessibility-audit/SKILL.md · Run a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use…
git:20260810.e5bc675 · audit A · 1,100 stars
ads-creative-development SKILL.md skill
rampstackco/claude-skills · skills/ads-creative-development/SKILL.md · How to produce ad creative that converts at performance scale. Hook patterns, format selection, video pacing, variation…
git:20260810.63d8377 · audit A · 1,100 stars
ads-performance-analytics SKILL.md skill
rampstackco/claude-skills · skills/ads-performance-analytics/SKILL.md · How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks…
git:20260810.e5bc675 · audit A · 1,100 stars
after-action-report SKILL.md skill
rampstackco/claude-skills · skills/after-action-report/SKILL.md · Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture…
git:20260810.e5bc675 · audit A · 1,100 stars
ai-content-collaboration SKILL.md skill
rampstackco/claude-skills · skills/ai-content-collaboration/SKILL.md · How humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid…
git:20260507.ac2b078 · audit A · 1,100 stars
analytics-strategy SKILL.md skill
rampstackco/claude-skills · skills/analytics-strategy/SKILL.md · Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and…
git:20260507.ac2b078 · audit A · 1,100 stars
art-direction SKILL.md skill
rampstackco/claude-skills · skills/art-direction/SKILL.md · Direct visual and creative work for campaigns, photography, illustration, video, and branded experiences. Use this…
git:20260810.1d637e9 · audit A · 1,100 stars
backlog-triage SKILL.md skill
rampstackco/claude-skills · skills/backlog-triage/SKILL.md · Turn an inbox of raw requests (bug reports, feature asks, support escalations, feedback, incident follow-ups) into a…
git:20261116.f6e91d9 · audit A · 1,100 stars
backup-and-disaster-recovery SKILL.md skill
rampstackco/claude-skills · skills/backup-and-disaster-recovery/SKILL.md · Plan and run backups, set recovery objectives, and run disaster recovery drills. Use this skill when defining RPO/RTO…
git:20260507.ac2b078 · audit A · 1,100 stars
beta-program-management SKILL.md skill
rampstackco/claude-skills · skills/beta-program-management/SKILL.md · Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection…
git:20260810.e5bc675 · audit A · 1,100 stars
brand-archetype-system SKILL.md skill
rampstackco/claude-skills · skills/brand-archetype-system/SKILL.md · Apply pre-composed aesthetic archetype defaults to jumpstart brand design work covering color, typography, layout…
git:20260510.f1aa1d7 · audit A · 1,100 stars

Every file in rampstackco/claude-skills

Browse by kind, by grade A, or by owner.