Spec Driven Test
Use specification-based testing methodology for end-to-end testing of web applications. Use this skill when users request "test this feature", "check this feature completeness", "do E2E testing on this project", "test this web app with an agent", or directly mention spec-driven-test / specification-based testing. This skill also applies to scenarios where users want to automatically generate test specs and test cases from code, then execute tests through browser automation. Even if users don't explicitly mention "spec" or "test case", if they want to systematically and automatically test a spe
Install
npx skills add Loveforwa/spec-test.skill --skill spec-driven-testgit clone --depth 1 https://github.com/Loveforwa/spec-test.skill.git /tmp/spec-test.skill
mkdir -p ~/.claude/skills
cp -r /tmp/spec-test.skill/en ~/.claude/skills/spec-driven-testPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Spec-Driven Test Use specification-based testing methodology for end-to-end testing of web applications. The entire process is completed through collaboration of three agents: **Cartographer** reads code to generate specs and test cases, **Inspector** reviews test cases using methodologies, **Operator** executes tests in real browsers. Two rounds of human review ensure quality. --- ## On-Demand Loading Navigation (Read This Before Executing Skill) This is a file-based skill—you **do not need to read all reference files at once**. Load corresponding sections by role and phase to significantly save tokens. **Identify your role and only read the corresponding main file**: - **Cartographer role** → Read `references/cartographer.md` (read sections by phase, see TOC at top of file) + Phases 0 / 1 / 2 / 2.5 / 3—only read the current phase section + After identifying matching scenario patterns at end of phase 1, **only read the matching** `references/scenarios/<corresponding-file>.md`, don't read all + When writing specs read `templates/spec-template.md`, when writing test cases read `templates/test-cases-template.md` - **Inspector role** → Read `references/inspector.md` (read sections by step, see TOC at top of file) + Workflow §1 / 1.5 / 1.6 / 1.7 / 1.8 / 2 / 2.5 / 3 / 4 + When selecting methodologies, **only read the matching** `references/methodologies/<corresponding-file>.md`, don't read all + For output format read `templates/judge-output-template.md`
Details
- Skill name
spec-driven-test- Repository
- Loveforwa/spec-test.skill
- Path
en/SKILL.md- Repo updated
- 24 May 2026
FAQ
What does the Spec Driven Test skill do?
Use specification-based testing methodology for end-to-end testing of web applications. Use this skill when users request "test this feature", "check this feature completeness", "do E2E testing on this project", "test this web app with an agent", or directly mention spec-driven-test / specification-based testing. This skill also applies to scenarios where users want to automatically generate test specs and test cases from code, then execute tests through browser automation. Even if users don't explicitly mention "spec" or "test case", if they want to systematically and automatically test a spe
How do I install the Spec Driven Test skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Loveforwa/spec-test.skill --skill spec-driven-test. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Spec Driven Test popular?
It lives in Loveforwa/spec-test.skill, which has 32 GitHub stars and 3 forks.
Related skills
Spec Driven Test
32Loveforwa/spec-test.skill
用规约驱动测试(specification-based testing)的方法对 web 应用做端到端测试。当用户说要"测试一下这个功能"、"检查一下这个功能的完整性"、"对这个项目做 E2E 测试"、"用 agent 测这个 web 应用"或者直接提到 spec-driven-test / specification-based testing 时使用这个 skill。也适用于用户希望基于代码自动生成测试规约和测试用例,然后通过浏览器自动化执行测试的场景。即使用户没有明确说"规约"或"测试用例"这些词,只要他想系统地、自动化地测试一个 web 项目的某个功能,都应该使用这个 skill。
Injection Testing
49mn-youssef/security-skills
Use when dynamically testing whether untrusted input reaches an interpreter — SQL/NoSQL injection (incl. blind/time-based), OS command injection, server-side template injection (SSTI), XXE, LDAP/XPath, and CRLF/header injection. Confirms on a running app what security-code-audit finds in source.
Uw Unity Feature Scaffold
47devdavv/unity-ai-workflow
Create a complete feature module with folder structure, Assembly Definition (.asmdef), test assembly, and namespace. Use when adding a new feature, system, or module to a Unity project. Triggers on requests like "create a new feature", "scaffold a module", "add a combat system", "I need a health system", "set up inventory", "create a new module for X", "add a new system", "new feature folder", or any task requiring new folders, assemblies, or namespaces for a gameplay feature — even when the user just names a system they want to build from scratch. Reads ProjectConfig.yaml for folder_strategy
File Upload and Ssrf
49mn-youssef/security-skills
Use when testing file-upload handling, server-side request forgery (SSRF), and insecure deserialization — upload bypasses (type/extension/content, polyglots, path traversal), SSRF to cloud metadata and internal services, and unsafe deserialization sinks. On apps you own or are authorized to test.
Uw Unity Test Runner
47devdavv/unity-ai-workflow
Generates EditMode and PlayMode tests using NUnit, mapped from GDD Gherkin scenarios. Use when writing tests, validating features, ensuring code quality, or verifying behavior after changes. Triggers on requests like "write tests for this", "test the health system", "add unit tests", "verify this works", "add PlayMode tests", "test this feature", "write integration tests", "make sure this doesn't break", "add test coverage", "TDD this feature", or any task involving test creation, test-driven development, or quality assurance. Maps Given/When/Then scenarios directly to test methods using NUnit
Business Logic Testing
49mn-youssef/security-skills
Use when testing application-specific workflow and business-rule flaws that scanners cannot find — price/quantity/parameter tampering, workflow and state-machine bypass, race conditions and TOCTOU, replay, and abuse of coupons/refunds/limits. Requires understanding what the app is supposed to do.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.