harden

Generate defensive specifications from PMR incident postmortems.

Updated Feb 23, 2026

Search Tags:#harden #error-boundary #test-spec #pmr #defensive-spec #type-spec

Ready to run

npx skills add https://github.com/0xHoneyJar/construct-hardening --skill harden-0xhoneyjar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harden
Source: https://github.com/0xHoneyJar/construct-hardening/tree/main/skills/harden
Command: npx skills add https://github.com/0xHoneyJar/construct-hardening --skill harden-0xhoneyjar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Postmortem-driven hardening often ends with incomplete recommendations. Harden provides a structured translation from PMRs into actionable defensive artifacts that guide sprint planning and implementation without writing code.

Core Features & Use Cases

Read a PMR and extract its Signal Gaps, Blast Radius, and existing Hardening Actions.
Generate four artifact types: Test Specs, Type Specs, Error Boundary specs, and reusable Checklists for migrations.
Update PMR records with proposed actions to streamline sprint planning and regression checks.
Use during signal audits to close gaps and drive concrete defenses.

Quick Start

Run the command /harden PMR-<id> after identifying a PMR with signal gaps to generate action specifications.

Frequently Asked Questions about harden

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

FAQPage Schema

How do I convert a postmortem report into actionable hardening specifications?▼

Postmortem-driven hardening closes incident gaps by translating PMR records into forward-looking defensive specifications like test specs, type definitions, and error boundaries. It ensures incomplete recommendations become concrete artifacts for sprint planning and regression checks.

How do I extract signal gaps and blast radius from a PMR to create test specs?▼

You can generate defensive artifacts from a PMR by running a command like /harden PMR-id. This reads the incident record, extracts signal gaps and blast radius, and outputs structured test specs, type specs, error boundaries, and checklists without writing implementation code.

What is the best way to generate error boundaries and type definitions from incident postmortems?▼

The best way to generate error boundaries and type definitions from incident postmortems is using a PMR translation tool. It processes incident signals and outputs structured defensive specs, including error boundary definitions and type specs, to guide hardening work without writing code.

Can I use postmortem-driven hardening to update sprint planning and regression checks?▼

Yes, you can use postmortem-driven hardening for sprint planning and regression checks. It updates PMR records with proposed actions and generates verification criteria, streamlining the integration of defensive specifications into your development cycles.

Does the hardening specification process require writing code during artifact generation?▼

No, the hardening specification process does not require writing code during artifact generation. It translates incident postmortems into implementation-agnostic artifacts like test specs, type definitions, and error boundaries to guide hardening work without writing code.