skills.rest
controlaltnerd
controlaltnerdCOMMUNITY
Explore all skills by this author →
GitHub

test-spec

Create and update test specifications using Given/When/Then format.

Updated Jan 28, 2026
Search Tags:#testing#quality assurance#specifications#acceptance criteria#test management#given-when-then
One-click install
npx skills add https://github.com/controlaltnerd/arc --skill test-spec-controlaltnerd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-spec
Source: https://github.com/controlaltnerd/arc/tree/main/.github/skills/test-spec
Command: npx skills add https://github.com/controlaltnerd/arc --skill test-spec-controlaltnerd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of defining, updating, and reviewing test specifications, ensuring clear acceptance criteria and test coverage.

Core Features & Use Cases

  • Create New Specs: Define acceptance criteria for new features using Given/When/Then format.
  • Update Existing Specs: Document test results, coverage, and status changes.
  • Review Specs: Understand expected behavior and edge cases before implementation.
  • Use Case: When a new feature is approved, use this Skill to create a detailed test specification outlining all scenarios, edge cases, and expected outcomes, which then guides the development and testing process.

Quick Start

Use the test-spec skill to create a new test specification for the user login feature.

Frequently Asked Questions about test-spec

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

FAQPage Schema
How do I write test specifications using Given-When-Then format?▼

Test specifications using Given-When-Then format define concrete scenarios and edge cases to establish clear acceptance criteria. You structure each scenario with a given context, a triggering action, and the expected outcome to guide development.

What is the best way to document acceptance criteria for new features?▼

Documenting acceptance criteria for new features requires outlining all scenarios and expected outcomes in a structured test specification. This enforces clear test coverage and defines expected behavior before implementation begins.

How do I update existing test specifications with test results and coverage?▼

Updating existing test specifications involves recording test results, documenting coverage status, and tracking changes to expected behavior. This maintains accurate quality assurance records as your feature evolves.

Can I use test specifications to review edge cases before implementation?▼

Yes, reviewing test specifications allows you to understand expected behavior and identify edge cases before implementation. Structured documentation ensures all testable scenarios are evaluated against the required acceptance criteria.

When do I need to use structured test management for quality assurance?▼

Structured test management for quality assurance is needed when a new feature is approved and requires detailed specifications. It enforces documenting all scenarios and expected outcomes to ensure comprehensive test coverage.

Related Skills

Explore More Software Engineering Skills→
Intense-VisionsIntense-Visions
18

harness-product-spec

Generate structured product specifications with EARS acceptance criteria from GitHub issues.

Official
Advanced
semicolon-devteamsemicolon-devteam

run-tests

Run Gradle tests for Spring Boot Kotlin projects and generate JaCoCo coverage reports.

Official
Advanced
thanh-abaiithanh-abaii
34

spec

Transform user intent into structured specifications through a five-phase process.

Community
Advanced
tarunccettarunccet
5

test-scenarios

Generate step-by-step test scenarios with objectives and expected outcomes from user stories and acceptance criteria.

Community
Intermediate