Individual skill

exploratory-test-charter

Write session-based exploratory testing charters to find what scripted tests miss. Use when asked to plan exploratory testing, write a test charter, design a testing session, or do risk-based exploration of a feature. Produces focused charters — a mission, areas/risks to explore, tactics and oracles, and timeboxed sessions — so exploration is purposeful and accountable, not random clicking.

plugins/pm-qa/skills/exploratory-test-charter/SKILL.md

Read pinned source

Source commit e0009a385c480fb0b5687e7412df67c7c64f7cee

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,541
Repository last updated
Nov 11, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Exploratory Test Charter Skill

Exploratory testing finds the bugs scripts don't — but only when it's *chartered*: a clear mission, a defined
area, and a timebox, so it's purposeful and you can report what was covered. This skill writes session-based
charters that point skilled testing at the riskiest areas, with the tactics and oracles to know when something
is wrong.

## Working from a brief

Given "explore the new checkout flow", **write the charters anyway** — infer the risk areas, useful tactics,
and oracles, labelling assumptions. Prioritise by risk. Never hand back a question instead of charters.

## Required Inputs
Back to top