write-metrics

Generate a domain metrics document with north-star, inputs, guardrails, baselines, and measurement sources.

1|Updated Apr 25, 2026

Search Tags:#planning #metrics #goals #measurement #product #north-star

Ready to run

npx skills add https://github.com/daddia/space --skill write-metrics

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-metrics
Source: https://github.com/daddia/space/tree/main/.agents/skills/write-metrics
Command: npx skills add https://github.com/daddia/space --skill write-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a structured, reusable metrics document that defines a domain's north-star metric, supporting inputs, guardrails, baselines, and measurement sources to guide discovery and roadmap decisions.

Core Features & Use Cases

Generate a domain-specific Metrics.md (using template.md) that ties product objectives to measurable signals.
Outline north-star, input metrics, guardrails (performance, reliability, experience), baselines, and phase targets.
Integrate with existing artifacts (product.md, roadmap.md, requirements.md) to ensure alignment across teams.

Quick Start

Invoke the domain metrics skill with a domain name to generate a complete metrics document and template files.

Frequently Asked Questions about write-metrics

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

FAQPage Schema

How do I define a north-star metric and supporting metrics for a product domain?▼

Defining a north-star metric and supporting metrics requires standardizing inputs, guardrails, baselines, and measurement sources into a structured document to guide product discovery and align teams.

What's the best way to align teams on product success criteria during roadmap planning?▼

Aligning teams on product success criteria involves mapping a metrics document to artifacts like product.md, roadmap.md, and requirements.md to ensure measurable objectives and actionable targets.

How do I create a metrics document that ties product objectives to measurable signals?▼

Creating a metrics document that ties product objectives to measurable signals generates a domain-specific metrics file outlining performance, reliability, and experience guardrails alongside phase targets.

Can I integrate domain metrics generation with existing product and roadmap artifacts?▼

You can integrate domain metrics generation with existing artifacts by mapping the metrics document to product.md, roadmap.md, and requirements.md to ensure alignment across teams and planning phases.

What should be included in a domain metrics document for product discovery?▼

A domain metrics document for product discovery should include the north-star metric, supporting input metrics, guardrails for performance and reliability, baselines, measurement sources, and phase targets.

When do I need a structured metrics document for product planning?▼

You need a structured metrics document for product planning when applying domain discovery to align teams on objectives, establish success criteria, and set actionable targets tied to measurable signals.