Generate Gherkin feature files from BR-FUTURE-NNN mappings for acceptance criteria.
npx skills add https://github.com/Adgmed2018/visa --skill visa-inspector
Please help me install this Agent Skill. Skill: visa-inspector Source: https://github.com/Adgmed2018/visa/tree/main/agents/visa-inspector Command: npx skills add https://github.com/Adgmed2018/visa --skill visa-inspector
Visa Inspector defines how to prove that the product meets the discovered specification before any code exists. It outputs executable acceptance criteria and Gherkin tests, providing a clear, technology-agnostic contract between spec and implementation.
Invoke the Visa Inspector to generate executable acceptance tests from the discovered specification before coding begins.
High-intent search queries and answers about installing and using this skill.
To generate Gherkin acceptance tests from a specification, you formalize acceptance criteria that prove the product matches the discovered spec. This produces executable technology-agnostic feature files guarding against drift between spec and implementation.
Specification traceability maps canonical IDs, such as BR-FUTURE-NNN, directly to executable acceptance tests. This parity ensures future code adheres to the discovered specification and guards against drift during development.
Yes, you can evaluate production readiness by iteratively refining BR-FUTURE-NNN mappings and assessing acceptance test coverage. This verifies that the implementation matches the discovered specification before code exists.
You formalize technology-agnostic acceptance criteria by codifying the discovered specification into executable Gherkin feature files. This creates a clear contract between spec and implementation without relying on specific technologies.
Yes, generating Gherkin feature files requires applying BR-FUTURE-NNN mappings to ensure traceability. This mapping links the executable acceptance tests directly back to the canonical specification IDs.
The best way to maintain parity between a discovered specification and future code is to generate executable acceptance tests and Gherkin feature files. This creates a verifiable contract that guards against drift throughout development.
Adgmed2018Convert conceptual domain models into canonical SDD artifacts for paridade-guard validation.
LaunchPadLabReview feature specifications for completeness and generate missing Gherkin scenarios.
PREDICTifExecutes implementation plans with verification steps and checkpoint reviews.
CaptainCrouton89Automate software tests to verify functionality against acceptance criteria.
