Platform Package Hardening

What problem does it solve?

Many shared packages drift into unreliable behavior with unclear contracts, brittle human output, and downstream breakage, leaving platform teams hesitant to ship improvements.

Core Features & Use Cases

• Compatibility Envelope: capture known consumers, supported environments, stability promises, and downstream compat sets before touching a package, using templates like platform-package-consumption-audit.
• Contract Hardening: tighten human-first outputs, config precedence, and error guidance while adding targeted tests that lock the seams and avoid breaking changes.
• Verification & Documentation: run existing unit tests, lint/format checks, downstream compat commands, and update the package README/docs with stable contract details, failure modes, and usage examples.
• Use Case: Apply this to a brownfield CLI package by stabilizing CLI output, adding golden tests, and proving fixes against representative downstream scripts.

Quick Start

Ask the Platform Package Hardening skill to review the package scope, harden the contract seams with tests, and document a downstream compat set.