Enforce verification-first workflows for software development tasks.
npx skills add https://github.com/kvithayathil/agent-resources --skill vdd
Please help me install this Agent Skill. Skill: vdd Source: https://github.com/kvithayathil/agent-resources/tree/main/skills/vdd Command: npx skills add https://github.com/kvithayathil/agent-resources --skill vdd
This Skill solves the pervasive problem of shipping buggy, unreliable code by enforcing a verify-before-trust discipline, ensuring no behavior is considered complete without a verifiable check to confirm it works as intended.
Use the vdd skill to implement the new user profile update endpoint, defining all acceptance criteria and verification tests before writing any implementation code.
High-intent search queries and answers about installing and using this skill.
Verification-driven development prevents shipping buggy code by enforcing a verify-before-trust discipline that gates task completion on passing all functional correctness checks. You define verifiable specifications first, then implement logic to satisfy those checks.
The best way to structure tests for new feature implementation is to define verifiable specifications and acceptance criteria upfront, write failing tests first, then implement the logic, and run mutation testing to confirm the tests catch real bugs before shipping.
Yes, you can apply formal verification and static analysis to code refactoring. The workflow supports layering verification strategies from type systems to formal methods, ensuring reliability and correctness are maintained throughout the refactoring process.
Yes, you need Python and jq along with gh and shasum installed in your environment to execute the static analysis, property-based testing, and verification workflows that gate code correctness checks.
Verification-driven development extends standard TDD by covering the full verification spectrum, including type-level checks, integration tests, and formal verification for API contract design, matching risk levels to appropriate verification strategies rather than relying solely on unit tests.
You should not use formal verification for every software testing workflow when the risk level does not justify the overhead; instead, match the verification strategy to the risk, using lighter checks like type systems or static analysis for lower-risk code.
ProyectoG007Monitor AI environments for security advisories and verify software integrity.
eng-vmessiahAutomate regression tests validating API response shapes and state integrity.
bobmatnycDerive a three-level testing pyramid from function code contracts.
mikivujkovicGuide feature delivery through DDD, BDD, TDD, and Git phases.
