skills.rest
i-standard1
i-standard1OFFICIAL
Explore all skills by this author →
GitHub

gen-test-specs

Generate system and UAT specifications from templates and requirements.

6|2|Updated Apr 5, 2026
Search Tags:#templates#specification#requirements#generate#uat#system-test
One-click install
npx skills add https://github.com/i-standard1/yamasaki --skill gen-test-specs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gen-test-specs
Source: https://github.com/i-standard1/yamasaki/tree/main/.claude/skills/gen-test-specs
Command: npx skills add https://github.com/i-standard1/yamasaki --skill gen-test-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the generation of system testing and UAT specifications from predefined templates, reducing manual drafting time and ensuring consistency across projects.

Core Features & Use Cases

  • Template-driven generation of system and UAT specs from the repository's templates.
  • Requirement-to-spec derivation: converts documented requirements in docs/ into test specs (system, UAT).
  • Use Case: Given a set of requirements in docs/requirements and an API spec in docs/api/openapi.yaml, it produces docs/tests/system-test-spec.md and docs/tests/uat-spec.md.

Quick Start

Invoke the gen-test-specs skill to generate system and UAT specs from your templates and existing requirements, API, and design docs.

Frequently Asked Questions about gen-test-specs

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

FAQPage Schema
How do I generate system and UAT test specs from existing requirements?▼

Generate system and UAT test specs by invoking the skill to load templates from docs/templates/phase4, derive test cases from requirements in docs/requirements, and populate docs/tests/system-test-spec.md and docs/tests/uat-spec.md.

What inputs do I need to automate UAT specification generation from templates?▼

Automating UAT specification generation requires documented requirements in docs/requirements, an API definition in docs/api/openapi.yaml, and design references in docs/design to populate the output spec files.

Does generating test specifications from templates work with OpenAPI definitions?▼

Generating test specifications from templates works with OpenAPI definitions by reading the API spec located at docs/api/openapi.yaml and deriving corresponding test cases for the system and UAT spec documents.

Can I use template-driven test spec generation for projects without design docs?▼

Template-driven test spec generation is designed for projects with design references in docs/design. While it primarily requires docs/requirements and API definitions, design docs provide necessary context for accurate spec derivation.

What is the best way to ensure consistency when creating system test specifications?▼

The best way to ensure consistency in system test specifications is using a template-driven generation process that loads predefined templates from docs/templates/phase4 and automatically commits the populated spec files.

Related Skills

Explore More Software Engineering Skills→
i-standard1i-standard1
6

implement-spec

Convert requirements and design documents into implementation plans, code, tests, and reviews.

Official
Advanced
AnjinMeiliAnjinMeili

qa-strategy

Generate a QA strategy artifact with test matrices, UAT criteria, regression scenarios, and observability guidelines.

Community
Advanced
softmgsoftmg

github-workflow-automation

Automate GitHub Actions workflow generation and CI/CD pipeline management.

Official
Advanced
NextSpark-jsNextSpark-js

cypress-e2e

Write Cypress End-to-End UAT tests with POM and BDD patterns.

Official
Advanced