Tracker Builder

Tracker Builder

When to use

Build actual .xlsx tracker — Daily Log tab feeding Summary via live formulas — replicating practice profile pattern, not generic template.

What this skill does not do

• Does not define metrics — route to /performance:metrics-glossary or /performance:kpi-tree-builder first.
• Does not invent raw input columns — ask for actual source fields.
• Does not redesign existing tracker — extends/replicates profile pattern.

Preconditions

Provisional mode

No existing pattern in profile: default Daily Log + Summary with AVERAGEIFS/SUMIFS movement columns; document formula logic tab.

Trust spine

• Confidence bands (structured-aggregation):
  • High: Live formulas wired; raw inputs separate from calculated; formula doc included.
  • Medium: Some raw inputs INPUT NEEDED flagged in notes.
  • Low: Metric list undefined — halt build.
• Failure modes:
  • Strategic advice vs. support: Tracker is draft structure for owner validation.
  • Client confidentiality: Tracker may contain proprietary metrics — CONFIDENTIAL header on docs.
  • Accountability gap: Formula logic documented for maintainability.
  • Analytical Rigor: Completeness — every summary metric traces to log inputs.
  • Incentive Gaming: N/A — build focus.
• Escalation triggers: Raw input unspecified — flag, don't invent column.

Workflow

1. Read practice profile for existing tracker structure.
2. Confirm metric list and category codes.
3. Design Daily Log — one row per period, columns for raw inputs only.
4. Design Summary — movement columns via AVERAGEIFS/SUMIFS per profile pattern.
5. Build .xlsx with live formulas per xlsx skill guidance.
6. Document formula logic in notes tab or section.
7. Flag unspecified raw inputs — don't invent.
8. Connector seed data. When seeding from ~~bi analytics or ~~spreadsheet MCP pulls, tag imported figures [sourced: <connector>, <workbook/dataset>, <as-of>] in the tracker notes tab; never paste uncited connector numbers into Summary formulas.
9. Completeness check before delivery.

Output format

Deliverable: .xlsx with Daily Log + Summary tabs (minimum), formula documentation, file path confirmed with user.

TRACKER LOCATION: [path]
METRICS INCLUDED: [list]
FORMULA PATTERN: [AVERAGEIFS/SUMIFS/etc.]
INPUT GAPS: [raw inputs not yet specified]

Worked example

Input: Three B2 metrics; profile shows SUMIFS on date column; weekly periods.

Expected output: .xlsx with Daily Log date column + three raw input columns; Summary rows with current/prior/change via SUMIFS; notes tab listing formula references.

Quality checks before delivering

• Formulas live, not static values
• Raw inputs separate from calculated metrics
• Pattern matches profile or documented default
• Formula logic documented
• Unspecified inputs flagged not invented

Propose profile update

When a stable convention surfaces during this run (thresholds, naming, tone, output format, or recurring corrections), propose a profile update: show the exact diff against ~/.claude/plugins/config/claude-for-strategy/performance/CLAUDE.md (org-wide facts go to org-profile.md), ask for confirmation, and write only on yes. Only /performance:practice-setup auto-applies a full profile write.

Outputs

Follows plugin CLAUDE.md § Outputs. Next: populate Daily Log, performance-narrative once data exists, or metrics-glossary for new metrics.