Generate defensive specifications from PMR incident postmortems.
npx skills add https://github.com/0xHoneyJar/construct-hardening --skill harden-0xhoneyjar
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
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.
Run the command /harden PMR-<id> after identifying a PMR with signal gaps to generate action specifications.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
0xHoneyJarGenerate structured Postmortem Records from git history and incident data.
ldk-hubExecutes story implementations from spec files across sprint workflows with built-in validation.
Dhruvipatel0514Generate defensive Bash scripts for threat detection, logging, and prevention.
haxlysConverts threat models and business context into actionable security requirements and test plans.
