attest

Solid

Verifying spec compliance: extracts ACs from specs, adversarially checks conformance, generates BDD scenarios and traceability matrices. Use when impl must be proven to match a PRD/SRS/AC.

AI & Automation 81 stars 14 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
64
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- CAPABILITIES_SUMMARY: - spec_compliance_verification: Adversarial verification of implementation against specifications - acceptance_criteria_extraction: Testable criteria extracted from spec documents under the ISO/IEC/IEEE 29148 quality gate - bdd_scenario_generation: Given/When/Then generation with priority-based minimums and quality-attribute validation - traceability_matrix: Bidirectional spec-to-code traceability with coverage analysis - adversarial_probing: Six-category probe framework (Boundary, Omission, Contradiction, Implicit, Negative, Concurrency) - compliance_reporting: Evidence-based verdicts (CERTIFIED/CONDITIONAL/REJECTED) with IEEE 1012-2024 V&V classification and integrity-level depth calibration - ambiguity_detection: Specification quality assessment and ambiguity flagging - remediation_routing: Handoff to Builder/Radar/Scribe for fixes - supply_chain_provenance: Optional evidence fields (`sbom_ref` / `signature_ref` / `provenance_attestation`) for SLSA-style conformance — advisory without Sigstore/Fulcio/Rekor/SBOM infra, blocking only under Tier policy - fix_prompt_generation: Paste-ready LLM Fix Prompt per confirmed AC gap (AC ID, AC verbatim, BDD scenario, verdict, evidence, recommended action, acceptance criteria, ruled-out alternatives, "what NOT to do") so Builder or Scribe/Scribe[unified] can act without reformulation; suppressed for verification-only, escalated rewrites, pending stakeholder decisions, or full conformance COLLABORATION_PATTER...

Details

Author
simota
Repository
simota/agent-skills
Created
8 months ago
Last Updated
1 weeks ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

accord

Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision, L1 Requirements, L2 Team Detail, L3 Acceptance Criteria). Use for cross-team specs.

81 Updated 1 weeks ago
simota
AI & Automation Listed

verify-impl

Forensic audit of an implementation against its authoritative specification. Use whenever a specification document and an implementation are both in scope and the user asks any conformance question - even when not phrased explicitly: 'does this code match the spec', 'verify this implementation', 'check spec conformance', 'audit compliance between design and code', 'is the implementation faithful', 'verify spec coverage', 'audit against requirements', 'spec-vs-code'. Also triggers when a file path under `.specs/` is mentioned alongside an implementation. Do NOT use for general code review, specification design review before implementation begins, security review, or architecture review without a spec document. Pass both the spec and the implementation scope as arguments; the skill does not infer them from the conversation.

6 Updated yesterday
sergeyklay
AI & Automation Listed

spec-probe

Run before implementing anything non-trivial: surface omitted edge cases and must-NOT constraints into a verification-tiered TASK_CONTRACT.md, so the verifier has something to check against. Use when starting a feature, a bugfix with unclear intended behavior, or any task where a reviewer would have to guess what correct means. Also use when asked to spec-probe, write a task contract, or check what the spec left out.

5 Updated 6 days ago
ucsandman