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.
npx skills add mohitagw15856/pm-claude-skills --skill exploratory-test-charter --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Working from a brief
- Required Inputs
- Output Format
- Exploratory Testing Charters: [feature]
- Quality Checks
- Anti-Patterns
- Based On
What does the exploratory-test-charter skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill exploratory-test-charter --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.