principle-progress-tracking git:20260904.5a122b3A

Immutable. This exact content is served forever at /api/v1/blob/5255291ca0eaed8d.

---
name: principle-progress-tracking
description: 'Requires one live ledger for ordered procedures. Apply when executing two or more dependent steps.'
user-invocable: false
---

# Progress Tracking

A convention, not a gate: create no artifact and block nothing; expose progress so ordered steps cannot be silently skipped.

- For procedures with two or more ordered steps, seed one todo per step before starting; omit one-item ledgers.
- Without a todo tool, state the ledger once inline and name each step as it completes.
- Track numbered steps, not phases or files; for unnumbered procedures, track each natural unit such as a slice, question, or hard-gate finding, never each guidance sentence.
- Mark each item `in_progress` at start and `completed` when landed, matching `team-fix`.
- Let the orchestrator—the main Claude Code session—own one phase ledger.
- Let agents track skill sub-steps only inside their contexts; never merge or read across orchestrator and agent ledgers.
- Let directly invoked standalone skills own their ledgers.
- Apply `skills/qrspi-workflow/SKILL.md` for the orchestrator TodoWrite phase-ledger contract.