test-idea-rewriting

Transform passive "Verify X" test descriptions into active, observable test actions.

1|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/aquariuscook/Agent_Modus_Map --skill test-idea-rewriting-aquariuscook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-idea-rewriting
Source: https://github.com/aquariuscook/Agent_Modus_Map/tree/main/.claude/skills/test-idea-rewriting
Command: npx skills add https://github.com/aquariuscook/Agent_Modus_Map --skill test-idea-rewriting-aquariuscook

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common issue of poorly defined test ideas that use passive language like "Verify X," making them difficult to implement and automate. It transforms these into clear, actionable steps with observable outcomes.

Core Features & Use Cases

  • Actionable Test Transformation: Converts "Verify X" statements into "[ACTION] [trigger]; [OBSERVE] [result]" format.
  • Verb Categorization: Provides guidance on using appropriate action and outcome verbs for different test types (UI, API, Data, Performance).
  • Use Case: A tester writes "Verify login works." This Skill transforms it into "Submit valid credentials; confirm session created," providing a clear, testable instruction.

Quick Start

Use the test-idea-rewriting skill to transform the test idea "Verify that the user profile page loads correctly".

Frequently Asked Questions about test-idea-rewriting

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

FAQPage Schema
How do I rewrite passive test cases like "Verify X" into actionable steps?

To rewrite passive test cases, the Skill transforms "Verify X" statements into the actionable format "[ACTION] [trigger]; [OBSERVE] [result]" using regex pattern matching and action verb categories. This improves testability and specificity for quality assurance workflows.

What is the best way to improve test design specificity for automated test execution?

Improving test design specificity involves categorizing action and outcome verbs for different test types like UI, API, Data, and Performance. This Skill applies transformation rules to convert vague test ideas into clear, observable test actions, making them easier to automate.

How does transforming test ideas into action verbs help QA workflows?

Transforming test ideas into action verbs helps QA workflows by shifting passive descriptions to observable outcomes. It identifies "Verify" patterns and applies categorized action verbs, resulting in testable instructions that reduce ambiguity during implementation.

Can I use this transformation pattern for both API and UI test design?

Yes, you can use this transformation pattern for both API and UI test design. The Skill provides specific guidance on applying appropriate action and outcome verbs across various test types, including UI, API, Data, and Performance testing.

Are there limitations to using regex for identifying test patterns to rewrite?

A limitation of using regex for identifying test patterns is that it specifically targets "Verify" statements. If a test description uses alternative passive phrasing without the targeted keyword, the transformation rules based on action verb categories will not apply.