create-manual-test-instructions
Turn a ticket or requirements document into a concise QA manual-test file a non-author can follow. Invoke manually only.
Install
npx skills add https://github.com/eai-org/agent-toolkit/tree/main/skills/create-manual-test-instructions
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install eai-org-agent-toolkit@llmmart
git clone https://github.com/eai-org/agent-toolkit.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole eai-org/agent-toolkit collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Create manual test instructions
Read the input ticket or requirements document (and, where needed for accurate navigation, the
code it cites). Write the manual-test file in the same directory, naming it by replacing
.REQUIREMENTS or .TICKET with .MANUAL-TEST (e.g. FOO.REQUIREMENTS.md →
FOO.MANUAL-TEST.md); if the input follows neither convention, append .MANUAL-TEST before
.md. If there is no file (pasted text), follow the project's/user's convention for where plans
live (default: .agents/plans/), derive a kebab-case <slug> from the content, and write
<slug>/<slug>.MANUAL-TEST.md there. Running forked, you can't ask mid-run: flag any guessed
location or slug in the final message for the user to verify.
The file must be followable by someone unfamiliar with the ticket — short but complete. Four parts:
- What changed — 1–2 sentences: the feature and the user-visible difference.
- How to get there — concrete navigation to the affected area (entry point, page/screen name, any prerequisite state).
- Before vs after — how the area behaved before, how it should behave now.
- What to verify — checklist of behaviors to confirm, including edge cases (empty values, multiple items, boundaries) where relevant.
Do not modify any source files; the only file you write is the manual-test document.
When done, state the manual-test file's project-relative path.
Files (agent-toolkit)
-
SKILL.md 1.6 KB
--- name: create-manual-test-instructions description: Turn a ticket or requirements document into a concise QA manual-test file a non-author can follow. Invoke manually only. context: fork license: MIT metadata: version: "1.4" --- # Create manual test instructions Read the input ticket or requirements document (and, where needed for accurate navigation, the code it cites). Write the manual-test file in the **same directory**, naming it by replacing `.REQUIREMENTS` or `.TICKET` with `.MANUAL-TEST` (e.g. `FOO.REQUIREMENTS.md` → `FOO.MANUAL-TEST.md`); if the input follows neither convention, append `.MANUAL-TEST` before `.md`. If there is no file (pasted text), follow the project's/user's convention for where plans live (default: `.agents/plans/`), derive a kebab-case `<slug>` from the content, and write `<slug>/<slug>.MANUAL-TEST.md` there. Running forked, you can't ask mid-run: flag any guessed location or slug in the final message for the user to verify. The file must be followable by someone **unfamiliar with the ticket** — short but complete. Four parts: 1. **What changed** — 1–2 sentences: the feature and the user-visible difference. 2. **How to get there** — concrete navigation to the affected area (entry point, page/screen name, any prerequisite state). 3. **Before vs after** — how the area behaved before, how it should behave now. 4. **What to verify** — checklist of behaviors to confirm, including edge cases (empty values, multiple items, boundaries) where relevant. Do not modify any source files; the only file you write is the manual-test document. When done, state the manual-test file's **project-relative path**.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.