# Blocker Reporting Outcome Validation

> Pattern for closing issues where the deliverable is documented blockers rather than feature completion

- Skill: `vamseeachanta/blocker-reporting-outcome-validation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vamseeachanta/blocker-reporting-outcome-validation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vamseeachanta/blocker-reporting-outcome-validation/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: vamseeachanta (https://skillmd.com/u/vamseeachanta)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vamseeachanta/blocker-reporting-outcome-validation

---


# Blocker-Reporting Outcome Validation

When an issue's acceptance criteria include explicit blocker documentation rather than feature completion: (1) Run existing test suite to validate ledger/index backing and content hashes; (2) Generate a blocker-reporting artifact (e.g., YAML handoff) that lists each target with its blocker reason; (3) Verify all targets have either valid summaries OR documented blockers; (4) Cross-reference artifact paths in handoff comments to #2227 or next-phase issue; (5) Close the issue with acceptance criteria met via blocker documentation, not feature delivery.