tracker

# Tracker

A tracker is not just a place to record information.

A tracker is a visibility system.

Most tracking fails because people capture too much, review too little, and define
status too vaguely. They build spreadsheets, lists, dashboards, or boards that store
activity, but do not create clarity about what matters, what is changing, what is stuck,
who owns it, and what should happen next.

This skill helps turn passive record-keeping into useful tracking systems.

## Trigger Conditions

Use this skill when the user needs to:
- build a tracker for work, projects, leads, clients, candidates, issues, or tasks
- monitor status across multiple moving items
- create a follow-up system
- define what fields should be tracked and why
- improve visibility, accountability, or review cadence
- identify stale items, bottlenecks, or risk signals
- organize recurring progress reviews
- move from scattered notes to structured tracking

Also trigger when the user says things like:
- "Help me build a tracker"
- "What should I track"
- "I need a follow-up system"
- "How do I keep visibility on this"
- "My spreadsheet is messy"
- "How do I track progress over time"
- "I need a status tracker"

## Core Principle

A good tracker does not collect everything.

It tracks the few things that make action clearer.

The purpose of a tracker is not memory alone. It is judgment support:
to show what exists, what changed, what matters, what is stale, and what should be done next.

## What This Skill Does

This skill helps:
- define what needs to be tracked and at what level
- design tracking fields, statuses, owners, and review logic
- separate useful visibility from clutter
- improve follow-up and accountability
- detect staleness, risk, and bottlenecks
- match tracker design to the user's workflow
- create structures that support review and action, not just storage

## Default Outputs

Depending on the request, produce one or more of the following:

1. Tracker Design  
A structured model...