What problem does it solve? Ad-hoc exploratory testing sessions often lack structure, making it hard to capture what was tested, what was found, and what should happen next. This Skill turns a feature and a risk hypothesis into a consistent, one-page charter and a ready-to-fill findings template. ## Core Features & Use Cases - Charter Generation: Produces a structured exploratory charter with mission, scope, time box, probe areas, oracles, and session setup derived from your feature and risk inputs. - Findings Template: Outputs an empty findings document with session metadata, observations, questions, issues table, coverage notes, and follow-ups. - Format-Only Discipline: Keeps output structure consistent without prescribing heuristics or exploration strategy — the testing judgment stays with the human. - Use Case: Before testing a new program-name validation field, ask for a charter with the risk "special characters bypass client-side checks" and receive a time-boxed session plan plus a findings sheet to fill in during exploration. ## Quick Start Ask the assistant to create an exploratory charter for a specific feature with a stated risk concern, and it will return a filled charter template plus an empty findings template.
