skills/magnus919_agent-skills

Fork 0

mirror of https://github.com/magnus919/agent-skills.git synced 2026-09-11 19:47:12 +03:00

Files

T

6b650b722c feat(product-analytics-and-measurement): add product analytics and measurement skill (#213 )

* feat(product-analytics-and-measurement): add product analytics and measurement skill

Add a new skill that turns intended product outcomes into observable,
governed evidence: metric trees with leading/lagging indicators and
countermetrics, event/tracking plans with identity/session/data-quality/
ownership considerations, instrumentation QA across client/server/pipeline/
end-to-end layers, dashboard contracts, privacy-aware measurement, and
decision cadence for outcome reviews.

Includes:
- SKILL.md with Loading Guide, When to Use/Not to Use, related-skill routing
- README.md with all 5 required human-facing sections
- references/discovery-brief.md mapping ownership boundaries vs existing skills
- references/metric-tree.md with measurability gates and contextual examples
- templates/tracking-plan.md (event taxonomy, identity resolution, privacy)
- templates/instrumentation-qa-checklist.md (4-layer QA)
- templates/outcome-review.md (decision cadence template)
- evals/evals.json with 6 cases covering new feature, internal product,
  public service, conflicting metrics, unmeasurable North Star rejection,
  and privacy-boundary measurement
- Updated root README catalog, skill-triggers.md, and regenerated catalogs

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

* feat(product-analytics-and-measurement): add product analytics and measurement skill

Add a new skill that turns intended product outcomes into observable,
governed evidence: metric trees with leading/lagging indicators and
countermetrics, event/tracking plans with identity/session/data-quality/
ownership considerations, instrumentation QA across client/server/pipeline/
end-to-end layers, dashboard contracts, privacy-aware measurement, and
decision cadence for outcome reviews.

Includes:
- SKILL.md with Loading Guide, When to Use/Not to Use, related-skill routing
- README.md with all 5 required human-facing sections
- references/discovery-brief.md mapping ownership boundaries vs existing skills
- references/metric-tree.md with measurability gates and contextual examples
- templates/tracking-plan.md (event taxonomy, identity resolution, privacy)
- templates/instrumentation-qa-checklist.md (4-layer QA)
- templates/outcome-review.md (decision cadence template)
- evals/evals.json with 6 cases covering new feature, internal product,
  public service, conflicting metrics, unmeasurable North Star rejection,
  and privacy-boundary measurement
- Updated root README catalog, skill-triggers.md, and regenerated catalogs

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

---------

Co-authored-by: username <username>
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

2026-08-02 16:58:08 -04:00

4.2 KiB

Raw Permalink Blame History

Product Outcome Review Template

A recurring review that ties product measurements back to decisions. Run monthly (recommended) or at whatever cadence matches the product's decision rhythm. This is not a status update — it is a deliberate inspection of whether the metrics are telling the truth and whether the team is acting on what they say.

Review Header

Field	Value
Product	[fill: product name]
Review date	[fill: date]
Review period	[fill: e.g. January 2026]
Participants	[fill: names and roles]
Facilitator	[fill: name]

1. North Star Health

[fill: Current North Star value and trend. Is it moving in the intended direction? At what rate?]

Metric	Current value	Previous period	Change	Trend	Context label
[North Star]	[fill]	[fill]	[fill: absolute and %]	[up/down/flat]	[Product/Market/Stage/Model]

Assessment: [fill: Is the North Star healthy? Is it still the right North Star?]

2. Metric Tree Health

[fill: For each node in the metric tree, record current value, target, and trend.]

Metric	Current	Target	Trend	Owner	Action status
[Driver 1]	[fill]	[fill]	[up/down/flat]	[team]	[on-track / needs-attention / critical]
[Sub-driver 1a]	[fill]	[fill]	[up/down/flat]	[team]	[on-track / needs-attention / critical]
...	...	...	...	...	...

Largest positive mover: [fill: which metric improved most, and why?]

Largest negative mover: [fill: which metric declined most, and why?]

3. Countermetric Audit

[fill: For each primary metric that drives a decision, verify that its countermetric has not crossed the guardrail threshold.]

Primary metric	Countermetric	Countermetric value	Threshold	Status
[metric]	[counter]	[value]	[threshold]	[ok / warning / breached]

Breached guardrails: [fill: Any countermetric that crossed its threshold. What action is taken?]

4. Decision Log

[fill: What decisions were made in this review period based on metric signals? What was the outcome of decisions made in the previous review period?]

Decision	Date	Trigger metric(s)	Expected outcome	Actual outcome	Learning
[decision]	[date]	[metrics that informed it]	[expected]	[actual]	[what we learned]

5. Instrumentation Health

[fill: Summary of instrumentation QA status. Any events with data quality issues? Any new events added? Any events deprecated?]

Check	Status
New events QA'd and approved this period	[fill: count and list]
Events with data quality alerts this period	[fill: count and list]
Deprecated events pending removal	[fill: count and list]
Tracking plan version	[fill: current version]

6. Metric Deprecation and Retirement

[fill: Any metrics that are no longer used for decisions? Any dashboards that should be retired?]

Metric / Dashboard	Reason for deprecation	Retirement date	Consumer notification
[name]	[why]	[date]	[teams notified]

7. Measurement Gaps and Requests

[fill: What would the team like to measure but cannot currently? What instrumentation constraints need investment to resolve?]

Gap	Constraint	Estimated effort	Priority
[desired measurement]	[missing instrumentation, data source, or identity resolution]	[effort]	[P0-P3]

8. Next Period Actions

[fill: Concrete actions for the next review period, with owners.]

Action	Owner	Due
[action]	[person/team]	[date]

Review Sign-Off

Role	Name	Date
Product owner	[name]	[date]
Engineering lead	[name]	[date]
Data / analytics lead	[name]	[date]

4.2 KiB Raw Permalink Blame History