verifying-and-adapting

Verify implementations against story-level behavioral specs and reconcile divergences.

2|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/chriswch/praxis --skill verifying-and-adapting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verifying-and-adapting
Source: https://github.com/chriswch/praxis/tree/main/skills/verifying-and-adapting
Command: npx skills add https://github.com/chriswch/praxis --skill verifying-and-adapting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Verify and reconcile what was actually implemented against the story-level behavioral spec after a TDD cycle, ensuring acceptance criteria are truly satisfied, surfaced divergences are documented, and the correct next action is chosen.

Core Features & Use Cases

  • Holistic acceptance checks: Walk every acceptance criterion against tests and edge cases to catch gaps where tests pass but do not implement the specified behavior.
  • Spec reconciliation: Update the behavioral spec inline for refined or diverged ACs and record rationale so the spec remains the source of truth.
  • Emergent knowledge capture and routing: Summarize design decisions, assess downstream slice impact for multi-slice features, and produce a definitive routing decision (done, next_slice, rework, escalate) with structured results in the artifact directory.
  • Traceable output: Produce a human-readable verification summary and a machine-readable results file to drive workflow routing and automated bookkeeping.

Quick Start

Run verifying-and-adapting after a TDD session completes to validate all ACs, update the spec if needed, capture emerged design notes, and write the routing decision to the artifact results file.

Frequently Asked Questions about verifying-and-adapting

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

FAQPage Schema
How do I verify TDD implementation against behavioral specifications?

To verify TDD implementation against behavioral specifications, run a verification process that walks every acceptance criterion against tests and edge cases, producing a summary and routing decision to confirm story completion.

What is spec reconciliation after a TDD cycle?

Spec reconciliation after a TDD cycle is the process of updating the behavioral spec inline for refined or diverged acceptance criteria and recording rationale so the spec remains the source of truth.

How do I route next steps after completing a TDD session?

To route next steps after completing a TDD session, assess downstream slice impact for multi-slice features and produce a definitive routing decision like done, next_slice, rework, or escalate via structured results files.

Can I update acceptance criteria inline when implementation diverges from the spec?

Yes, you can update acceptance criteria inline when implementation diverges from the spec by applying spec reconciliation to document changes and capture rationale for the diverged behaviors.

What's the best way to capture emergent design decisions during story verification?

The best way to capture emergent design decisions during story verification is to summarize them alongside acceptance checks and write both human-readable and machine-readable results files to drive workflow routing.

Why do my tests pass but do not implement the specified behavior?

Tests pass but do not implement the specified behavior when acceptance criteria are not holistically walked against edge cases, which is solved by running a post-TDD verification to catch gaps between tests and specs.