agentleFS
tiago-oliveira-catiago-oliveira-ca/zenodotus-harness/skills/testing/SKILL.md

testing

Skill1 starsChanged 8 days agoMITView on GitHub

Software testing documentation dispatcher. Use when creating, reviewing, or improving test specifications and test documentation. Trigger on: "write test cases", "create a test plan", "test specification", "STS", "TDS", "TCS", "TPS", "test procedure", "define exit criteria", "requirements traceability matrix", "RTM", "risk-based testing", "test environment", "non-functional testing", "accessibility testing", "security testing", "performance testing", "CI/CD test integration", "document how to test this feature", "IEEE 829", or any task producing or reviewing software test documentation.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When a test documentation task is requested, load the appropriate sub-skill.

    line 15

“Common” is measured: kept by at least 6 in 10 of the 172 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Testing Dispatcher

When a test documentation task is requested, load the appropriate sub-skill.

Routing Table

Task TypeWhen to UseSub-skill to load
Software Test Specification (STS)Writing or reviewing test specs, test cases, test procedures, RTMs, exit criteria, IEEE 829 / ISO 29119 standardssoftware-test-specification/SKILL.md

Instructions

  1. Load software-test-specification/SKILL.md for all test documentation tasks. This dispatcher currently routes 1:1 — the broad trigger surface in the description (risk-based testing, RTM, non-functional testing, CI/CD integration) all funnels to that one sub-skill, which covers those areas in its sections. The dispatcher is kept as a scaffold for future test-doc sub-skills.
  2. For test requirements (the performance/security/availability targets a test verifies), the source artifact lives in the documentation tree: ../documentation/non-functional-requirements-standards/SKILL.md.
  3. This dispatcher covers test documentation artifacts only (STS/TDS/TCS/TPS, RTMs, exit criteria). For TDD/BDD development practice in Python — Canon TDD, classicist/mockist, Gherkin authorship, Kafka event-driven testing — see ../code-standards/python/references/ddd-tdd-bdd-workflow.md instead; it is not a test-documentation skill and does not route through here.
  4. For test code and execution — actually writing and running tests, as opposed to test-planning documents — this dispatcher does not own that lane. Load the relevant zeno-stack testing-execution leaf instead: zeno-stack/zeno-python-testing, zeno-stack/zeno-react-testing, zeno-stack/zeno-e2e-testing, or zeno-stack/zeno-browser-qa.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.