record-signal

What problem does it solve?

Records a benefit metric signal outside of a /definition-of-done run.

Use when you have measurement evidence for a metric — e.g. after running a real session, reviewing usage data, or receiving user feedback — and want to update the pipeline without running a full DoD. Asks which feature, which metric, what you observed, then writes signal, evidence, and lastMeasured to pipeline-state.json. Use when someone says "record a signal", "update a metric", "we got data", "the metric moved", "log a measurement", or "mark metric as on track".

Core Features & Use Cases

• Lightweight signal capture: writes to pipeline-state.json without requiring a full DoD run
• Records observations and updates to the metric's signal and lastMeasured for progressive visibility
• Use Case: after a session or data review, capture evidence and move the metric toward its target

Quick Start

Record a new observation for a selected metric and update pipeline-state.json accordingly.