What problem does it solve? Without quantitative baseline data, teams cannot prove whether a solution actually improved anything. This Skill guides Phase 2 MEASURE of a work package by collecting current-state metrics, defining measurable success targets, and documenting reproducible measurement methods before any analysis or design begins. ## Core Features & Use Cases - Baseline Capture: Produces a structured *-baseline.md artifact with numeric current-state values, measurement conditions, and data sources using the provided template. - Success Metric Definition: Enforces the format "metric improves from baseline to target measured by method" so every work package has verifiable exit criteria. - Measurement Methodology Reference: Includes guidance on outcome vs. proxy metrics, measurement conditions, and tools such as k6, Lighthouse, jest --coverage, and EXPLAIN ANALYZE. - Use Case: Before optimizing a slow API endpoint, run this Skill to record the current P95 latency of 450ms, set a target under 100ms, and document the k6 benchmark procedure so Phase 11 can verify the improvement. ## Quick Start Ask the assistant to start Phase 2 MEASURE for the active work package and document the baseline metrics and success targets.
