metrics-management
Manage metric specifications and observations: quantified measures the project cares about (velocity, error rates, lead time, NPS). Use when defining or recording a quantitative measure: team velocity, error rate, lead time, customer satisfaction score.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- metrics-management
- metadata
- { "processkit": { "id": "SKILL-metrics-management", "uses": [ { "skill": "event-log", "purpose": "Log events to keep the audit trail accurate after every write." } ], "layer": 4, "created": 1775433600000, "version": "1.0.0", "category": "devops", "provides": { "templates": [ "metric-spec" ], "primitives": [ "Artifact", "LogEntry" ] }, "apiVersion": "processkit.projectious.work/v2" } }
- description
- Manage metric specifications and observations: quantified measures the project cares about (velocity, error rates, lead time, NPS). Use when defining or recording a quantitative measure: team velocity, error rate, lead time, customer satisfaction score.
02 资源文件 2
- 资产文件assets/metric-spec.yaml307 B
- 脚本scripts/.gitkeep—
03 SKILL.md 正文
Metrics Management
Intro
A metric specification is an Artifact with kind: metric-spec that names a
quantified measure the project cares about. Examples: team velocity per
sprint, p99 latency, release frequency, error rate, customer NPS.
Overview
Metric spec vs observation
A metric-spec Artifact defines what is measured. Individual readings are
LogEntries (event_type: metric.recorded) or external time-series data.
processkit stores the definition, not the time series.
Shape
---
apiVersion: processkit.projectious.work/v2
kind: Artifact
metadata:
id: ART-velocity-metric-spec
created: 2026-04-06T00:00:00Z
spec:
name: velocity
kind: metric-spec
description: "Story points completed per sprint."
unit: points
direction: higher-is-better
measurement: >
Sum of spec.estimate.value for WorkItems with spec.state=done in the
sprint's SCOPE.
target: 40
tolerance: "±20%"
cadence: sprint
owner: ACTOR-tech-lead
---
Recording observations
Individual measurements are LogEntries:
kind: LogEntry
spec:
event_type: metric.recorded
timestamp: 2026-04-14T17:00:00Z
actor: ACTOR-claude
subject: ART-velocity-metric-spec
subject_kind: Artifact
summary: "Sprint 42 velocity: 38 points"
details:
value: 38
scope: SCOPE-sprint-42
The index MCP server joins metric-spec Artifacts with their LogEntry observations to produce time series.
Gotchas
Agent-specific failure modes — provider-neutral pause-and-self-check items:
- Defining a metric spec without a measurement source. "We want to
improve velocity" is not a metric spec; "Story points completed per
sprint, measured from
query_workitems(state=done, scope=sprint-N)" is. Without a source, the metric can't be measured and becomes decoration. - Setting target values without a baseline. "Reduce error rate by 50%" is meaningless if you don't know the current rate. Always record the baseline when the metric spec is created, and update it explicitly when you reset goals.
- Confusing leading vs lagging indicators. A leading indicator predicts future outcomes (PR review turnaround time); a lagging indicator measures past outcomes (incidents per quarter). Don't optimize a lagging indicator if a leading one is available — feedback loops are slower.
- Metrics without owner or cadence. "Who looks at this and how often" is part of the metric definition, not an afterthought. Unowned metrics rot.
- Storing measurement values inline in the metric spec. Metric-spec artifacts define what is measured, not the measurements themselves. Time-series values belong in an external store (Prometheus, BigQuery, ...); the metric spec references the store, not the data.
- Vanity metrics that don't drive decisions. "Total LOC", "PR count", "tickets closed" sound impressive but don't predict anything actionable. If knowing the number wouldn't change what you do next, it's vanity — drop it.
- Hand-waving "trending up" without numbers. When asked about a metric's status, fetch the actual value from the source the metric spec points at; don't synthesize a trend from memory.
Full reference
Fields
| Field | Type | Notes |
|---|---|---|
name |
string | kebab-case identifier |
description |
string | What this metric measures |
unit |
string | points / ms / % / count / etc. |
direction |
enum | higher-is-better / lower-is-better / target |
measurement |
string | How to compute the value |
target |
any | Desired value (number or string) |
tolerance |
string | Acceptable deviation from target |
cadence |
string | How often it's measured |
owner |
string | Actor ID responsible for the metric |
active |
bool | false = no longer tracked |
Vanity metrics
Avoid metrics that always trend up just by activity (commits per week, lines of code) — they reward effort, not outcome. Favor metrics that can get worse when the project is unhealthy: lead time, defect rate, customer satisfaction, mean-time-to-recovery.
Metrics vs goals
A goal is a desired future state recorded in a Scope's spec.goals. A metric
spec is the quantitative thing the goal is measured by. One goal may reference
multiple metric specs; one metric spec may inform multiple goals.
04 同仓库更多 Skills
standard-ui-design
暂无简介
standard-agent-use
Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.
standard-agent-building
暂无简介
skill-management
Manage Skill package manifests as v1 ontology entities.
schema-management
Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.
proposition-management
Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.