harness-accept

Render acceptance criteria verification status and ship/wait/reject recommendations as HTML reports.

39|46|Updated May 29, 2026

Search Tags:#html #decision #demo #acceptance #harness #plan-brief

Ready to run

npx skills add https://github.com/maxwell2732/claudecode-research-harness-workflow --skill harness-accept

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harness-accept
Source: https://github.com/maxwell2732/claudecode-research-harness-workflow/tree/main/skills/harness-accept
Command: npx skills add https://github.com/maxwell2732/claudecode-research-harness-workflow --skill harness-accept

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a self-contained, auditable acceptance review by rendering an HTML report that summarises acceptance criteria and outputs a ship/wait/reject recommendation, helping non-engineers decide whether to ship a delivered task.

Core Features & Use Cases

Plan Brief integration: reads acceptance_criteria joined by user_request_hash from personal-preference.v1 to inform the demo.
Self-contained HTML rendering: creates a single-file HTML report that shows each criterion as verified or unverified and includes the final decision.
Decision support: computes a threshold-based recommendation (ship, wait, or reject) and provides evidence for auditability.
Use Case: a product manager requests an acceptance review before release, and the skill outputs a ready-to-share HTML demo with rationale.

Quick Start

Provide a concise, self-contained acceptance demo that presents criteria verification status and the recommended action in a single HTML page.

Frequently Asked Questions about harness-accept

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

FAQPage Schema

How do I generate an HTML acceptance demo for release decisions?▼

An HTML acceptance demo renders acceptance criteria verification status and a ship, wait, or reject recommendation into a single self-contained file. It joins stored criteria by user_request_hash to produce a shareable, auditable decision document for stakeholders.

What is threshold-based acceptance criteria evaluation for task release?▼

Threshold-based acceptance evaluation checks stored criteria from a Plan Brief, marks each as verified or unverified, and computes a final ship, wait, or reject recommendation. It provides evidence for non-engineers deciding whether to release a delivered task.

Can I share acceptance review results with non-engineer stakeholders without extra setup?▼

Yes, the acceptance review outputs a portable single-file HTML report requiring no dependencies. It summarises each criterion's verification status and the final decision, making it directly shareable with non-engineer stakeholders for audit purposes.

How do I retrieve acceptance criteria from a Plan Brief for review?▼

Acceptance criteria are read back from personal-preference.v1 storage and joined by user_request_hash. This retrieval feeds the HTML rendering so the demo accurately reflects the criteria originally defined in the Plan Brief.

What's the best way to create an auditable decision document before shipping a task?▼

A self-contained HTML acceptance demo provides an auditable decision document by displaying criteria verification status alongside a threshold-based ship, wait, or reject recommendation. It consolidates evidence into one portable file for release reviews.

When should I not use an automated HTML acceptance report?▼

Automated HTML acceptance reports are designed for non-engineer stakeholders reviewing pre-release tasks. They are not suited if acceptance criteria have not been stored in a Plan Brief beforehand, since the report depends on retrieving that data by user_request_hash.