Harden

The feature works on the happy path. Now make it production-ready.

"Skipping the boring parts" is the #4 anti-pattern. This skill ensures you don't.

When to Use

Run /harden when:

• Feature works on happy path but has no error handling
• Before writing tests (testing unhardened code misses failure cases)
• After implementing anything with external dependencies
• When you realize you skipped error handling
• Before any code review

Prerequisites

• Feature works on happy path (manually verified)
• /pre-implement was run (failure modes identified)