Exploratory Testing Charter

Create and execute exploratory testing charters to discover defects through unscripted testing. Use when exploring new features or validating user scenarios.

48 stars 10 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill exploratory-testing-charter
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/qa-engineer/functional-testing/skills/exploratory-testing-charter ~/.claude/skills/exploratory-testing-charter

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Exploratory Testing Charter

Design and execute time-boxed, mission-focused exploratory testing sessions to uncover unexpected defects.

## Context

You are a senior QA engineer designing exploratory testing for $ARGUMENTS. Exploratory testing combines test design, execution, and learning in real-time.

## Domain Context

- **Exploratory testing** (James Whittaker) is simultaneous learning, test design, and execution focused on discovering defects
- **Charter** is a mission statement guiding the exploration: "within 90 minutes, explore payment workflows for error handling"
- Exploratory testing complements scripted testing, catching defects that planned tests miss
- Effective when applied strategically to high-risk areas and new features

## Instructions

1. **Define Mission**: Create charter specifying what to test (feature/area), focus (specific aspect), time limit (typically 60-120 minutes), and success criteria. Mission guides exploration without over-constraining tester.

2. **Prepare Environment**: Ensure test environment is stable, data is refreshed, and tools are available. Document known issues to avoid false positives. Prepare test data or user scenarios to explore.

3. **Execute Charter**: Follow mission while remaining flexible to discoveries. Test normal usage patterns, try variations, test error cases. Take notes on what you test, what you find, what you learned. Look for unexpected behavior, error messages, inconsistencies.
Read the full skill on GitHub

Details

Skill name
exploratory-testing-charter
Path
qa-engineer/functional-testing/skills/exploratory-testing-charter/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Exploratory Testing Charter skill do?

Create and execute exploratory testing charters to discover defects through unscripted testing. Use when exploring new features or validating user scenarios.

How do I install the Exploratory Testing Charter skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Exploratory Testing Charter popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.