This is one skill of many.
Browse the full catalog to see everything your Righthand can take off your plate — and everything you can teach it later.
Product
Use when making sure every shipped feature has the event that proves it was used and the metric that says whether it worked: events as code, one metric per feature named in the spec, the one view of core metrics the founder recognizes, change-only weekly readouts, and the instrumentation issue for anything merged without a number. Maintains Knowledge/Organizations/metrics.md.
Skills travel in packs — pick one and your Righthand arrives already equipped with everything the job needs.
The answer before the question. Standups, delivery reviews, the numbers behind every shipped feature, and one honest status view, so what is in flight, what landed, and what it did are always a glance away.
The proof layer. Five core metrics the founder recognizes stay on one trusted view, every Monday says what changed and what it means, and every feature merged without an event gets an instrumentation issue the same week.
The engineering lead and product manager a founder wishes they could afford as one hire. Code shipped through coding agents against scenarios written first, delivery always visible, users listened to and measured, the system kept healthy, launches coordinated, and a rhythm that protects maker time.
Browse the full catalog to see everything your Righthand can take off your plate — and everything you can teach it later.