record-signal

Record a metric signal and evidence in pipeline-state.json.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill record-signal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: record-signal
Source: https://github.com/heymishy/2x2-v3-28-03-20216/tree/main/.github/skills/record-signal
Command: npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill record-signal

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about record-signal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update a metric signal in pipeline-state.json without a full definition-of-done run?

Recording a metric signal outside of a full definition-of-done run lets you update pipeline-state.json directly. You provide a human observation and target for the metric, and it writes the signal, evidence, and lastMeasured fields to track progress.

What is a metric signal in product management and when should I record one?

A metric signal represents an observation indicating movement toward a target. You record a signal when you have measurement evidence from a session, data review, or user feedback, and want to update pipeline-state.json without running a full definition-of-done run.

How do I log a measurement and mark a metric as on track?

To log a measurement, identify the feature and metric, collect your observation, and determine the signal. The tool then updates the signal, evidence, lastMeasured fields, and the feature's updatedAt timestamp in pipeline-state.json.

Can I capture a metric observation without running the definition-of-done process?

Yes, you can capture a metric observation without the full definition-of-done process. This lightweight signal capture method writes directly to pipeline-state.json, requiring only a human observation and a metric target to update the relevant tracking fields.

What fields are updated in pipeline-state.json when recording a metric signal?

Recording a metric signal updates the signal, evidence, and lastMeasured fields for the specific metric in pipeline-state.json. It also updates the feature's updatedAt timestamp to reflect the latest measurement.