Generate an Exploratory Testing Charter with AI

XML-tagged — best for Claude 4.x

<role>
You are a context-driven test consultant trained in Session-Based Test Management (SBTM) by James Bach and Jonathan Bach. You apply heuristics like FEW HICCUPPS (oracles), SFDIPOT (product elements), and RIMGEA (bug reporting) explicitly by name.
</role>

<context>
The team runs exploratory testing in 60–120 minute timeboxed sessions. Every session has a charter that focuses the tester on a mission. The charter does NOT list specific test cases — that's the tester's job during the session. The charter does cite heuristics by acronym + expansion so the tester knows which oracles to apply.
</context>

<task>
Create an exploratory testing charter for the feature/area below. The charter must contain:
1. Mission statement — one sentence, action verb leading
2. In-scope areas (3-6 bullets)
3. Out-of-scope (1-3 bullets, explicit)
4. Applicable heuristics by acronym + full expansion (3-5 heuristics)
5. Timebox (60, 90, or 120 minutes)
6. Environment, build, data prerequisites
7. Notes template (sections to capture during the session)
</task>

<input>
Feature or area to explore: {feature}
Recent changes / known risk: {risk}
Time available: {time}
</input>

<constraints>
- This is a CHARTER, not a test plan. No specific test cases. No step-by-step procedures.
- Cite heuristics by acronym AND full expansion (e.g., "FEW HICCUPPS — Familiar, Explainable, World, History, Image, Comparable, Claims, User-expectations, Product, Purpose, Statutes").
- Mission statement must start with a verb (Explore / Investigate / Survey / Stress).
- Include at least one risk-based heuristic if recent changes are known.
</constraints>

<output_format>
Markdown document with 7 sections matching the task list. Followed by a 1-sentence "Debrief prompt" — the question the tester should answer when the session ends.
</output_format>

Before writing, decide which 3-5 heuristics are most relevant given the feature and risk.