verifying-outcomes

Verify goal achievement with PASS, PARTIAL, or FAIL verdicts and line citations.

18|9|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/arozumenko/sdlc-skills --skill verifying-outcomes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verifying-outcomes
Source: https://github.com/arozumenko/sdlc-skills/tree/main/skills/verifying-outcomes
Command: npx skills add https://github.com/arozumenko/sdlc-skills --skill verifying-outcomes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents teams from falsely concluding that work is “done” by verifying whether the intended outcome is actually achieved using concrete evidence.

Core Features & Use Cases

  • Goal-backward verification: Restates the desired outcome as a concrete, testable statement before checking anything.
  • Evidence-based checks: Confirms what must be true, what must exist (with content), and what must be connected (integrations, wiring, and test execution).
  • Risk surfacing: Identifies where the outcome will likely break via edge cases, error paths, missing validation, and configuration gaps.
  • Use Case: Before closing an issue or merging a PR, verify that the user-visible behavior matches the goal—not that the checklist was merely completed.

Quick Start

Ask your AI to produce a verification report using the “state the goal, then verify TRUE/EXISTS/CONNECTED, and summarize PASS/PARTIAL/FAIL with line-cited evidence” output format for your change.

Frequently Asked Questions about verifying-outcomes

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

FAQPage Schema
How do I verify issue resolution with code evidence instead of just checking a task list?▼

Verifying issue resolution requires restating the goal as a testable outcome and performing repository reads, grep, and connectivity tracing to produce a PASS, PARTIAL, or FAIL verdict with path and line citations.

What is outcome validation in software delivery and why is it needed before a PR merge?▼

Outcome validation prevents teams from falsely concluding work is done by checking what must be true, what must exist with content, and what must be connected, ensuring user-visible behavior matches the goal before closure.

How do I validate that a code fix actually resolves the intended behavior using grep and glob checks?▼

You validate a code fix by restating the desired outcome as a concrete statement, then using repository reads, grep, and glob checks to confirm what must be true, exist, and be connected, yielding a cited PASS, PARTIAL, or FAIL verdict.

Does software delivery verification check for edge cases and missing validation paths?▼

Yes, software delivery verification surfaces risks by identifying where the outcome will likely break via edge cases, error paths, missing validation, and configuration gaps during the evidence-gathering process.

Can I review PR results by tracing integrations and wiring instead of relying on test execution alone?▼

Yes, PR result review traces integrations, wiring, and test execution as part of its evidence-based checks, confirming that required connections exist and validating the actual goal achievement before merging.

What is the best way to confirm a software feature is complete without running a manual checklist?▼

The best way to confirm feature completion is goal-backward verification, which restates the intended outcome as a testable statement and checks repository evidence to produce a line-cited PASS, PARTIAL, or FAIL summary.