What problem does it solve?
Making changes in the Happier repositories without a disciplined workflow leads to fixes in the wrong owner, duplicated logic, unverified behavior, and premature completion claims. This Skill enforces a structured implementation workflow that locates the canonical owner, preserves the full authorized scope, and validates the real outcome rather than the mere presence of code.
Core Features & Use Cases
- Canonical-owner discovery and corridor mapping: Identifies the authoritative owner of each behavior plus all affected callers, consumers, migrations, and compatibility paths before editing.
- Scope-preserving solution economy with TDD: Requires meaningful RED tests, minimal coherent GREEN implementation, and refactoring through the real consumed path instead of dormant scaffolding.
- Risk-appropriate validation and evidence-backed closeout: Distinguishes VERIFIED_COMPLETE, IMPLEMENTED_NOT_VERIFIED, PARTIAL, and BLOCKED outcomes, and handles GitHub issue linkage, commit attribution, and release-stage labeling rules.
- Use Case: When fixing a reported regression in the Happier CLI, the Skill guides reproduction at the smallest real boundary, root-cause analysis at the originating layer, a regression test, the owner-level fix, and an honest verification report.
Quick Start
Use the happier-implement skill to implement this change in the Happier repository and validate the real outcome end to end.
