Generates visual acceptance criteria from EARS requirements when specs lack an AC section.
npx skills add https://github.com/FredoAi/fredo --skill spec-test-gen-fredoai
Please help me install this Agent Skill. Skill: spec-test-gen Source: https://github.com/FredoAi/fredo/tree/main/.opencode/skills/spec-test-gen Command: npx skills add https://github.com/FredoAi/fredo --skill spec-test-gen-fredoai
## Acceptance Criteria section, leaving testers without concrete, verifiable checks. This Skill derives testable acceptance criteria directly from EARS requirements so end-to-end verification can proceed without modifying the original spec. ## Core Features & Use Cases - EARS Requirement Parsing: Extracts and classifies WHEN/WHILE/WHERE requirements by whether they are user-observable, skipping code-only requirements. - Concrete AC Generation: Produces verifiable ACs with specific text, roles, counts, or CSS selectors, prefixed with AC-A to distinguish them from spec-authored criteria. - Capsule Mapping: Resolves each REQ-ID to its capsule by reading issue comments via gh issue view, then writes a structured AC table to .opencode/tmp/<issue>/generated-acs.md. - Use Case: During e2e verification of backlog issue #42, the spec comment has no AC section. Load this Skill to parse its EARS requirements, generate a table of visual ACs mapped to capsules, and proceed with testing as if the ACs came from the spec. ## Quick Start Check the backlog issue's spec comment for a missing Acceptance Criteria section and generate testable ACs from its EARS requirements before running e2e verification.High-intent search queries and answers about installing and using this skill.
Parse each EARS requirement (WHEN/WHILE/WHERE patterns), classify whether it is user-observable, then write one concrete AC per observable requirement using specific text, roles, counts, or CSS selectors that a tester can verify with DOM tools.
Load this Skill when `gh issue view` reveals the spec comment has no `## Acceptance Criteria` section. It derives generated ACs from the EARS requirements and writes them to `.opencode/tmp/<issue>/generated-acs.md` so e2e testing can proceed.
Requirements about rendering, persistence, interactive updates, and input validation are user-observable and get ACs. Internal data structures and API response shapes are code-only and are skipped since they cannot be verified visually.
No. Generated ACs are written only to a scratch file under `.opencode/tmp/<issue>/` and prefixed with `AC-A` to distinguish them from spec-authored criteria. The spec and backlog are never modified.
Generated ACs are derived strictly from the EARS requirement text, so they cannot capture layout or behavior the requirements do not state. If a capsule cannot be resolved from issue comments, it is marked as `Capsule: Unknown (REQ-X)`.
hujianbestGenerate review-ready requirement specifications with traceability anchors and acceptance criteria.
KSD-COAutomate end-to-end QA testing with persistent headless Chromium via Playwright.
yoshisadaGenerate unit-test style checklists to validate requirement quality against spec sections.
opsMachineGenerate a structured Test Plan from an approved spec by mapping acceptance criteria to test types.