Attest

Extract acceptance criteria and generate BDD scenarios for compliance verification.

68|14|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/simota/agent-skills --skill attest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Attest
Source: https://github.com/simota/agent-skills/tree/main/attest
Command: npx skills add https://github.com/simota/agent-skills --skill attest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that software implementations strictly adhere to their specifications, preventing costly defects and ensuring product quality through rigorous verification.

Core Features & Use Cases

  • Specification Compliance Verification: Adversarially checks if code meets defined requirements.
  • Acceptance Criteria Extraction: Automatically pulls testable criteria from specification documents.
  • BDD Scenario Generation: Creates Given/When/Then scenarios for test automation.
  • Traceability Matrix: Maps specifications to implementation and tests.
  • Use Case: Before releasing a new feature, use Attest to verify that all critical acceptance criteria from the product spec have been met, generating a compliance report and identifying any deviations.

Quick Start

Use the attest skill to verify that the implementation in './src' matches the specification in './docs/spec.md'.

Frequently Asked Questions about Attest

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

FAQPage Schema
How do I verify software implementation compliance against a specification document?

To verify software implementation compliance, you adversarially check your code against the specification to extract acceptance criteria, generate BDD scenarios, and issue evidence-based compliance verdicts. This ensures strict adherence and prevents costly defects.

What is the best way to generate BDD scenarios from acceptance criteria?

Generating BDD scenarios from acceptance criteria involves extracting testable conditions from your specification and automatically creating Given/When/Then scenarios. This supports test automation and ensures your implementation matches defined product requirements.

Can I check specification compliance for SaaS, E-commerce, and Dashboard projects?

Yes, you can check specification compliance for SaaS, E-commerce, and Dashboard projects. The verification process supports quality gates, traceability, and ambiguity detection across these specific project types to ensure product quality.

How do I map specifications to implementation and tests for traceability?

To map specifications to implementation and tests for traceability, you generate a traceability matrix that connects your product requirements directly to the code and generated BDD scenarios. This identifies deviations before release.

Does specification verification work without external dependencies or modules?

Yes, specification verification works without external dependencies. The process relies entirely on your internal source code and specification documents to perform adversarial verification and extract testable acceptance criteria autonomously.