agentleFS
Sign inStart free
rpraharajrpraharaj/ai-sdlc/skills/charter-exploratory/SKILL.md

charter-exploratory

Skill0 starsChanged 17 days agoMITView on GitHub

Write time-boxed exploratory test charters from named risks. Use when the user asks for exploratory testing, charters, session-based test management, or /charter-exploratory. Do not invent risks. Do not declare pass without a charter log.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not invent risks. Do not mark the charter passed until a log exists.

    line 19
  2. Distinctive:

    Read AGENTS.md if present.

    line 41
  3. Distinctive:

    If writing after a session, fill the log from what the tester said.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Charter exploratory

Give testers a mission and a clock. This is not a case list (write-test-plan) and not write-tests.

Do not invent risks. Do not mark the charter passed until a log exists.

Is this the right skill?

SignalDo this instead
Scripted caseswrite-test-plan
Strategy / layerswrite-test-strategy
Defect write-uptriage-defect after the session

Required inputs

  • Risks from write-test-strategy or the user (named)
  • A time box per charter from the user (or unknown — need human)

Human decisions (do not invent)

  • Duration
  • Whether the session found a ship blocker

Procedure

  1. Read AGENTS.md if present. Read the test strategy risks.
  2. Find the home: docs/qa/charter-<slug>.md.
  3. Open references/charter-template.md. Copy every heading. Write n/a when unused.
  4. One charter per focused risk. Include: mission, time box, what to avoid, notes area for the session log.
  5. If writing after a session, fill the log from what the tester said. Do not invent bugs.

Output

  • Path: docs/qa/charter-<slug>.md
  • Template: references/charter-template.md

Quality bar

  • Each charter traces to a named risk
  • Time box is user-set or unknown — need human
  • Result is not run unless a log is present
  • Unused headings are n/a

Done

  1. Path
  2. Charter count
  3. Next skill: run the session, then triage-defect as needed

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free