test-architect

Designs risk-based test strategies, ATDD specifications, and adversarial review checklists for software quality engineering.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/rhorba/RestoLedger --skill test-architect-rhorba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-architect
Source: https://github.com/rhorba/RestoLedger/tree/main/skills/test-architect
Command: npx skills add https://github.com/rhorba/RestoLedger --skill test-architect-rhorba

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often write tests reactively without a strategy, leaving critical paths under-tested and low-risk areas over-tested. This Skill designs the test system itself: it prioritizes coverage by risk, writes acceptance criteria before code, and hunts for the edge cases and abuse scenarios that normal testing misses. ## Core Features & Use Cases - Risk-Based Test Strategy: Score components by failure impact, change frequency, and complexity to assign coverage levels, then define release gates and coverage targets per risk tier. - ATDD & BDD Specifications: Write Gherkin acceptance scenarios before development begins, turning approved specs into the regression suite. - Adversarial Review & Edge Case Hunting: Systematic checklists for input abuse, auth bypass, race conditions, business logic abuse, and boundary/type/time/state/network edge cases. - Use Case: Before building a payment feature, use this Skill to produce a risk-scored test strategy, Gherkin acceptance scenarios for lockout and refund flows, and an adversarial checklist covering double-submit and negative-amount attacks. ## Quick Start Ask the AI to design a risk-based test strategy with ATDD acceptance scenarios and an adversarial review checklist for your feature or user story.

Frequently Asked Questions about test-architect

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

FAQPage Schema
How do I create a risk-based test strategy?

Score each component by failure impact, change frequency, and complexity, then sum the scores to assign a test level. Scores of 13-15 get maximum coverage including adversarial and load tests, while scores of 1-4 get smoke tests only.

How to write ATDD acceptance criteria with Gherkin?

Write Given-When-Then scenarios before coding begins, covering happy paths, boundaries with scenario outlines, and error paths. Have the user review and approve the scenarios, then developers implement code until the specs pass and become the regression suite.

What is the difference between a test architect and a tester?

A test architect designs the test strategy, risk prioritization, acceptance specifications, and release gates for a feature or project. A tester writes individual test cases, runs suites, and reports bugs within that strategy.

When should I run an adversarial review?

Run adversarial reviews on auth changes, payment logic, PII handling, public API endpoints, file uploads, and any feature where a bug means a security incident or data loss. The checklist covers input abuse, auth bypass, race conditions, and business logic abuse.

What are the limitations of risk-based testing?

Risk scoring depends on subjective estimates of impact and frequency, so miscalibrated scores can under-test critical paths. It also requires discipline to keep low-risk areas at smoke-level coverage rather than letting test suites grow unchecked.