blocker-reporting-outcome-validation
Pattern for closing issues where the deliverable is documented blockers rather than feature completion
Best use case
blocker-reporting-outcome-validation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Pattern for closing issues where the deliverable is documented blockers rather than feature completion
Teams using blocker-reporting-outcome-validation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/blocker-reporting-outcome-validation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How blocker-reporting-outcome-validation Compares
| Feature / Agent | blocker-reporting-outcome-validation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Pattern for closing issues where the deliverable is documented blockers rather than feature completion
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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.
Related Skills
data-validation-reporter
Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.
orcaflex-reporting-fixture-proof-pattern
Build and extend fixture-backed OrcaFlex reporting proof paths in digitalmodel using stable metadata baselines, normalized HTML snapshots, and reusable reporting test helpers.
gtm-demo-validation-cache-regression-repair
Diagnose and repair GTM demo validation failures caused by legacy cache files missing intermediate chart data, especially in nested digitalmodel demo scripts using --from-cache.
plan-gated-issue-validation-workflow
Systematic validation pattern for plan-approved GitHub issues with pre-existing deliverables
overnight-verify-close-and-blocker-conversion
Use overnight Codex lanes to clear stale-open GitHub issues by verification-first closure, and convert blocked PR-repair attempts into dedicated blocker issues instead of speculative edits.
gtm-demo-validation-and-preview-gif-workflow
Validate digitalmodel GTM demos end-to-end, recover from legacy Demo 2 cache regressions, regenerate fresh artifacts, and produce lightweight preview GIFs for issue
github-actions-cross-platform-validation-gotchas
Execution-time GitHub Actions pitfalls discovered while fixing cross-platform CI workflows — path-filter non-triggers, Windows shell parsing mismatches, and job-scoped validation.
reporting-workflow
End-to-end workflow for generating reports from data, validating outputs, running report-focused tests, and iterating on HTML/interactive reporting artifacts.
semantic-taxonomy-reporting-consistency
Keep semantic-diff taxonomy summaries consistent with evidence tables when adding richer categories to legacy comparison/reporting pipelines.
data-validation
QA an analysis before sharing with stakeholders -- methodology checks, accuracy verification, and bias detection
plan-rerun-state-revalidation
Revalidate live plan state before rerunning adversarial review or resuming from a handoff so review prompts do not encode stale approval/artifact assumptions.
discipline-refactor-phase-4-validation
Sub-skill of discipline-refactor: Phase 4: Validation.