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
Ask for these only if they aren't already provided (else infer and label):
- The target — the feature/area and what it does.
- Risk & concerns — what's new/changed, what's complex, and where failure would hurt most.
- Context — users, platforms, data, and integrations involved.
- Time available — to size and prioritise the sessions.
Output Format
Exploratory Testing Charters: [feature]
Risk overview — the few areas most worth exploring and why (new, complex, high-impact, historically buggy).
Charters — one per focused session (Session-Based Test Management style):
Charter: Explore [area] using [tactics/data] to discover [information about risk].
- Areas / things to cover: the specific surfaces, flows, inputs, states.
- Test ideas & tactics: how to probe it — boundary values, interruptions, bad data, concurrency, navigation, roles/permissions, network conditions, etc.
- Oracles (how you'll know it's wrong): the spec, consistency, comparable products, user expectations, "would a user be annoyed?".
- Timebox: ~60–90 min (short/long), priority.
- Data / setup needed.
Provide 3–6 charters, prioritised by risk.
Reporting — what to capture per session: bugs found, areas covered vs. not, new risks/questions, and follow-up charters.
Quality Checks
Anti-Patterns
Based On
Session-Based Test Management (exploratory testing) — chartered, risk-prioritised, timeboxed sessions with explicit tactics and oracles.
Example Trigger Phrases
- "Plan exploratory testing."
- "Write a test charter."
- "Design a testing session."
- "Do risk-based exploration of a feature."
1---2name: exploratory-test-charter3description: "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."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/exploratory-test-charter7---89# Exploratory Test Charter Skill1011Exploratory testing finds the bugs scripts don't — but only when it's *chartered*: a clear mission, a defined12area, and a timebox, so it's purposeful and you can report what was covered. This skill writes session-based13charters that point skilled testing at the riskiest areas, with the tactics and oracles to know when something14is wrong.1516## Working from a brief1718Given "explore the new checkout flow", **write the charters anyway** — infer the risk areas, useful tactics,19and oracles, labelling assumptions. Prioritise by risk. Never hand back a question instead of charters.2021## Required Inputs2223Ask for these only if they aren't already provided (else infer and label):2425- **The target** — the feature/area and what it does.26- **Risk & concerns** — what's new/changed, what's complex, and where failure would hurt most.27- **Context** — users, platforms, data, and integrations involved.28- **Time available** — to size and prioritise the sessions.2930## Output Format3132### Exploratory Testing Charters: [feature]3334**Risk overview** — the few areas most worth exploring and why (new, complex, high-impact, historically buggy).3536**Charters** — one per focused session (Session-Based Test Management style):3738> **Charter:** Explore [area] using [tactics/data] to discover [information about risk].39> - **Areas / things to cover:** the specific surfaces, flows, inputs, states.40> - **Test ideas & tactics:** how to probe it — boundary values, interruptions, bad data, concurrency, navigation, roles/permissions, network conditions, etc.41> - **Oracles** (how you'll know it's wrong): the spec, consistency, comparable products, user expectations, "would a user be annoyed?".42> - **Timebox:** ~60–90 min (short/long), priority.43> - **Data / setup needed.**4445Provide 3–6 charters, **prioritised by risk**.4647**Reporting** — what to capture per session: bugs found, areas covered vs. not, new risks/questions, and follow-up charters.4849## Quality Checks5051- [ ] Each charter has a clear mission (explore X to discover Y about risk Z) — not "test the app"52- [ ] Charters are prioritised by risk, with the rationale stated53- [ ] Test ideas/tactics are concrete (boundaries, interruptions, bad data, roles…), not generic54- [ ] Oracles are named so the tester can recognise a problem55- [ ] Sessions are timeboxed and sized to the available time56- [ ] A lightweight reporting structure (coverage + findings) is included5758## Anti-Patterns5960- [ ] Do not write "explore the feature" with no mission, areas, or oracles — that's aimless clicking61- [ ] Do not skip prioritisation — explore the riskiest areas first62- [ ] Do not turn charters into scripted step-by-step cases — exploration needs freedom within focus63- [ ] Do not omit oracles — without them a tester can't tell right from wrong64- [ ] Do not leave sessions open-ended — timebox them so coverage is accountable6566## Based On6768Session-Based Test Management (exploratory testing) — chartered, risk-prioritised, timeboxed sessions with explicit tactics and oracles.6970## Example Trigger Phrases7172- "Plan exploratory testing."73- "Write a test charter."74- "Design a testing session."75- "Do risk-based exploration of a feature."