bostonaholic/progress-tracking
skills/progress-tracking/SKILL.md
Todo-first progress convention for multi-step procedures — loaded by every multi-step agent to track its own steps without drift
$ install --global
skillsauthnpx skillsauth add bostonaholic/team progress-trackingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 2, 2026, 3:13 AM248.4s1 file scanned
SKILL.md
- name:
- progress-tracking
- description:
- Todo-first progress convention for multi-step procedures — loaded by every multi-step agent to track its own steps without drift
- user-invocable:
- false
Progress Tracking
A convention, not a gate. It produces no artifact and blocks nothing. It shapes how any agent or skill executing a multi-step procedure keeps its own work visible, so steps are not silently skipped.
When it applies
When a procedure has two or more ordered steps, seed one todo item per step before starting and mark each complete as you go. A single-step procedure is exempt — a one-item ledger is noise.
Per-step granularity
One todo item per numbered step — not per phase, not per file. Mark each item
in_progress when its step starts and completed when that step lands,
matching how team-fix already marks each step. Keep items at the
granularity of the procedure's own numbered list.
Ledger ownership
The orchestrator (the main Claude Code session) owns the single phase-level ledger. An agent executing a multi-step skill tracks its own sub-steps within its own context and never merges them up into the orchestrator's phase ledger. A standalone, directly-invoked skill seeds its own ledger. The two ledgers live in separate ownership scopes and are never read across.
See also
The orchestrator's phase-level TodoWrite contract lives in
skills/qrspi-workflow/SKILL.md — the phase-ledger sibling of this
per-procedure convention.
Related Skills
bostonaholic/eng-design-doc-review
testing
VerifiedTrustedCommunity
Adversarially review a technical design document with fresh context before the human gate. Dispatches the built-in `general-purpose` subagent (clean context, no shared history with the design-author) against `docs/plans/<id>/design.md` and presents its verdict — APPROVE, REQUEST CHANGES, or COMMENT. Optional, not part of the QRSPI pipeline. Trigger on "review the design doc", "audit design.md", "is this design ready", or `/eng-design-doc-review`.
3SKILL.mdUpdated May 23, 2026
bostonaholic/code-review
development
VerifiedTrustedCommunity
Generator-evaluator separation and review methodology — loaded by review agents to enforce fresh-context review discipline, Conventional Comments format, and gate verdicts
3SKILL.mdUpdated May 2, 2026
bostonaholic/team-worktree
data-ai
VerifiedTrustedCommunity
Prepare one or more isolated git worktrees — one per repository the topic touches. Router action — no agent. Trigger on "set up the worktree", "isolate this work", or "/team-worktree".
3SKILL.mdUpdated Apr 23, 2026
bostonaholic/team-structure
development
VerifiedTrustedCommunity
Break the approved design into vertical slices with verification checkpoints. The structure document is the human's last review point before code is written. Trigger on "slice this up", "break the design into steps", or "/team-structure".
3SKILL.mdUpdated Apr 23, 2026