exploratory-test-writer

Frame risk-based exploratory testing intents and investigation orders for a product or feature.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/lespaceman/athena-workflow-marketplace --skill exploratory-test-writer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: exploratory-test-writer
Source: https://github.com/lespaceman/athena-workflow-marketplace/tree/main/plugins/exploratory-testing/skills/exploratory-test-writer
Command: npx skills add https://github.com/lespaceman/athena-workflow-marketplace --skill exploratory-test-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frame the reasoning and scope for exploratory testing by framing risks, hypotheses, and the investigation order before broader coverage planning.

Core Features & Use Cases

  • Frame risk hypotheses and investigation order for product features.
  • Produce an exploratory charter artifact that grounds testing efforts in evidence and context.
  • Guide downstream activities like capture-feature-evidence, plan-test-coverage, and test-case generation without over-committing to any single path.

Quick Start

Describe an initial exploratory charter for a feature by listing the top risks, justification, and the next follow-ups needed.

Frequently Asked Questions about exploratory-test-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an exploratory testing charter and why do I need one?▼

An exploratory testing charter frames risk hypotheses and investigation order for a product feature before coverage planning, grounding testing efforts in evidence and context to guide downstream test generation.

How do I write a risk-driven exploratory test charter?▼

To write an exploratory test charter, list the top product risks, provide justification, and define next follow-ups to frame the investigation order and guide downstream test coverage activities.

Can I use exploratory charters alongside structured test case generation?▼

Yes, exploratory charters guide downstream activities like test-case generation and plan-test-coverage without over-committing to any single path, ensuring structured coverage follows risk-based investigation.

What's the best way to plan exploratory testing before defining test coverage?▼

The best way to plan exploratory testing before coverage is to frame risk-based investigation orders, produce an exploratory-charter artifact, and cite evidence sources to prescribe concrete follow-ups.

When should I not use exploratory charters for software testing?▼

Avoid using exploratory charters when you lack defined product risks or evidence sources, as the artifact requires risk hypotheses and justification to frame investigation orders and guide downstream planning.