skills.rest
berlinguyinca
berlinguyincaCOMMUNITY
Explore all skills by this author →
GitHub

autospec-qa

Validate autospec implementations against source specs with evidence-backed UI, API, accessibility, and test coverage checks.

3|1|Updated Apr 29, 2026
Search Tags:#accessibility#ui testing#spec validation#autospec#qa revalidation#end-to-end evidence#test regeneration
One-click install
npx skills add https://github.com/berlinguyinca/autospec --skill autospec-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: autospec-qa
Source: https://github.com/berlinguyinca/autospec/tree/main/skills/autospec-qa
Command: npx skills add https://github.com/berlinguyinca/autospec --skill autospec-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures a running autospec implementation actually satisfies the written product specification, preventing “it looks done” releases by auditing UI behavior, validation, state transitions, API effects, accessibility, and evidence-backed test coverage.

Core Features & Use Cases

  • Spec traceability QA matrix: Produces a requirement-by-requirement PASS/FAIL/PARTIAL/NOT TESTED report so gaps are explicit instead of anecdotal.
  • UI + workflow revalidation: Audits user-input controls (enabled/disabled, discovery, valid/invalid/boundary inputs), workflow controls, failure banners, and cross-feature behavior.
  • No-mock deployed smoke + evidence-first verdicts: Requires deployed/dev, no-mock smoke coverage for user workflow controls and enforces a PARTIAL verdict when required smoke paths are NOT TESTED.
  • Test regeneration/strengthening plan: Regenerates or strengthens tests when coverage is missing or weak, converting QA findings into actionable follow-up issues.
  • Required artifacts and reliability gating: Produces machine-readable proof artifacts (proof matrix, reliability contract, control-intent ledger, mutation-proof, canary results when applicable) to support auditability and regression detection.

Quick Start

Use the autospec-qa skill to revalidate a feature spec against a running app by running: /autospec-qa --spec docs/specs/<feature>.md --url http://localhost:3000

Frequently Asked Questions about autospec-qa

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

FAQPage Schema
How do I validate that my running application matches the product specification?▼

You can validate a running application against a source spec by auditing UI behavior, API effects, accessibility, and test coverage. This process generates a requirement-by-requirement PASS/FAIL/PARTIAL/NOT TESTED matrix to make spec compliance gaps explicit.

How do I prevent false-green test verdicts in UI-heavy workflows?▼

Prevent false-green test verdicts by enforcing deployed, no-mock smoke requirements for user workflow controls. The validation process automatically assigns a PARTIAL verdict when required smoke paths are NOT TESTED, ensuring incomplete coverage is explicitly flagged.

What is spec traceability and how does it improve QA revalidation?▼

Spec traceability is a QA matrix mapping each product specification requirement to a PASS/FAIL/PARTIAL/NOT TESTED status. It improves revalidation by replacing anecdotal gap assessments with explicit, evidence-backed auditable proof artifacts.

How do I generate a test regeneration plan for weak automated tests?▼

Generate a test regeneration plan by auditing UI controls, validation rules, and state transitions to identify missing or weak coverage. The process converts these QA findings into actionable follow-up issues to strengthen automated tests.

Can I use spec validation to check accessibility and form control boundaries?▼

Yes, spec validation audits user-input controls including enabled/disabled states, discovery, valid/invalid/boundary inputs, and accessibility. It cross-references these checks against workflow controls and failure banners for comprehensive coverage.

What machine-readable proof artifacts are needed for regression detection?▼

Regression detection requires machine-readable proof artifacts including a proof matrix, reliability contract, control-intent ledger, and mutation-proof. These artifacts support auditability and ensure deployed applications satisfy written specifications.

Related Skills

Explore More Software Engineering Skills→
opensoftopensoft

speckit-specify

Wrap and delegate Speckit specification commands to a source skill.

Official
Intermediate
thisismynewfmail-uithisismynewfmail-ui

subagent-driven-development

Dispatch isolated subagents for implementation tasks with two-stage spec and quality reviews.

Community
Advanced
berlinguyincaberlinguyinca
3

autospec-release

Compute deterministic PASS/PARTIAL/FAIL release verdicts from QA evidence.

Community
Advanced
nnkiennnnkienn
1

webapp-testing

Run automated browser tests for web applications using Playwright.

Community
Intermediate