exploratory-test

# Exploratory Test Execute multi-level exploratory testing that goes beyond smoke testing to actively find bugs through escalating test scenarios. ## Task Tracking At the start, use `TaskCreate` to create a task for each step: 1. Load or create test plan 2. Determine testing approach 3. Run `/user-experience` skill (when user-facing) 4. Execute tests by level 5. Report ## Step 1: Load or Create Test Plan Resolve the test plan using these rules in order: 1. **Explicit path** — If a file path was passed, use it 2. **Explicit slug** — resolve to `.turbo/test-plans/<slug>.md` 3. **Anchoring artifact** — If the work under test is anchored to a plan, resolve to `.turbo/test-plans/<that-slug>.md` when that file exists 4. **Single file** — Glob `.turbo/test-plans/*.md`. If exactly one file exists, use it 5. **Most recent** — If multiple files exist, use the most recently modified 6. **Legacy fallback** — `.turbo/test-plan.md` if `.turbo/test-plans/` does not exist 7. **Nothing found** — run the `/create-test-plan` skill first, then use the plan it writes If multiple test plans exist and the most-recent choice is non-obvious, use `AskUserQuestion` to let the user pick from the candidates. Read the resolved test plan and state its path. Unless an explicit path or slug was passed, confirm the resolved plan still describes the work under test: - **Unavailable branch state** — a scenario's steps require a branch that no longer resolves in the repository - **Completed prior run*...