harness-feedback

Convert cross-project lessons into standardized harness rules, hooks, and standards.

8|1|Updated Feb 13, 2026

Search Tags:#feedback #governance #standards #rules #lessons #harness

Ready to run

npx skills add https://github.com/Heavy-Chain-Engineering/etc --skill harness-feedback

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harness-feedback
Source: https://github.com/Heavy-Chain-Engineering/etc/tree/main/skills/harness-feedback
Command: npx skills add https://github.com/Heavy-Chain-Engineering/etc --skill harness-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures discrete cross-project lessons from downstream work and converts them into structured harness rules, hooks, or standards to prevent recurring friction.

Core Features & Use Cases

Interactive lesson capture: prompts the operator to convert a lesson into a canonical harness artifact.
Auto-generates a 📬 Harness feedback block that routes to the etc harness spec or gates.
Enforces a closed-loop remediation pattern: can draft spec briefs or apply direct rule changes depending on context.

Quick Start

Begin by describing a discrete downstream lesson, then follow the prompts to render a structured 📬 Harness feedback block.

Frequently Asked Questions about harness-feedback

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

FAQPage Schema

How do I convert cross-project lessons into standardized rules?▼

To convert cross-project lessons into standardized rules, you describe a discrete downstream lesson and the skill interactively prompts you to generate a canonical harness artifact, such as a structured feedback block or adaptable spec brief, to prevent recurring friction.

What is the best way to capture process failures and manual workarounds as governance standards?▼

The best way to capture process failures and manual workarounds as governance standards is to use an interactive lesson capture mechanism that translates wasted time into structured harness rules and hooks, driving systemic improvements across projects.

How do I create harness hooks from real-world project lessons?▼

You create harness hooks from real-world project lessons by providing a discrete downstream lesson, which triggers the skill to auto-generate a structured harness feedback block that routes directly to your harness spec or gates for closed-loop remediation.

Do I need a specific output format to apply cross-project standards to my harness gates?▼

Yes, applying cross-project standards to your harness gates requires a canonical output format that includes a terminates_in gate reference, ensuring the generated hooks or spec briefs integrate correctly into your existing governance workflow.

Can I draft spec briefs instead of direct rule changes when routing harness feedback?▼

Yes, you can draft spec briefs instead of direct rule changes when routing harness feedback, as the skill supports an adaptable closed-loop remediation pattern that drafts spec briefs or applies direct rule changes depending on your specific context.

When should I not use automated lesson capture for governance rules?▼

You should not use automated lesson capture for governance rules if your downstream friction cannot be isolated into a discrete lesson, as the skill requires a specific discrete input to successfully translate process failures into standardized hooks.