A command that creates a visual report of a feature’s development phases, showing which are complete, active, or waiting. It reads the story’s phase state and plan, then checks Git history and files for evidence of progress.

Use it to track a story’s phases, display a progress bar and table, and identify work that is done, underway, or still pending.

It gives a quick view of feature progress without manually comparing planning files, commits, and unfinished work.

progress — Command by TouheedCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/touheedcode/claude-dev-workflow/progress

Clone the repo

git clone --depth 1 https://github.com/TouheedCode/claude-dev-workflow

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 742 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00742
Opus 5	$0.00000	$0.00371
Sonnet 5	$0.00000	$0.00148
Haiku 4.5	$0.00000	$0.00074

Measured yesterday against content hash 7ae9d8bdb1a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

progress scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/progress.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/progress — Visual Phase Progress

Arguments

$ARGUMENTS — Optional: story ID (e.g., "US-001"). If omitted, reads from .phase-context.json.

Instructions

You are generating a visual progress report showing which phases are complete, in-progress, or pending for the current feature.

Input: $ARGUMENTS

Step 1: Load State

Read .phase-context.json for the story ID and completedPhases array
Read the plan at docs/plans/PLAN-{story-ID}.md to get the full phase list
Run git log main..HEAD --oneline to detect any uncommitted phase work

Determine the status of each phase:

Done — listed in completedPhases and has a matching commit
Active — has deliverable files on disk but not yet in completedPhases (work in progress)
Pending — no files created yet

Step 2: Generate Progress Display

Print an ASCII progress bar and phase table:

  US-001: Todo List Management
  ================================================

  Progress: [################........] 4/7 phases (57%)

  Phase  Status   Title                    Files  Tests
  -----  -------  -----------------------  -----  -----
    1    [done]   Presentational UI          6     12
    2    [done]   API Client & Mocks         3      -
    3    [done]   Smart Components           3      4
    4    [done]   Repository Layer           4      8
    5    [    ]   Service Layer              -      -
    6    [    ]   Controller Layer           -      -
    7    [    ]   Integration                -      -

  Next step: /implement Phase 5
  ================================================

Active phase (work in progress):

  Progress: [################=>......] 4.5/7 phases

    5    [>>>>]   Service Layer              1/2    0/8

Step 3: Show Phase Dependencies

If the next pending phase has dependencies, show them:

  Dependencies for Phase 5:
    Phase 4 (Repository Layer)  [done]  -- provides repository interfaces

If dependencies are unmet:

  BLOCKED: Phase 5 requires Phase 4 to be completed first.
  Run: /implement Phase 4

Read the full file on GitHub · 96 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 96 lines · 0 tokens per session scan A 7ae9d8bdb1a8

Subscribe to this mod's changes

progress is a command published in the GitHub repository TouheedCode/claude-dev-workflow (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 742 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow Planning Productivity agentic-coding ai-agent ai-coding ai-workflow anthropic best-practices

progress

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/progress — Visual Phase Progress

Arguments

Instructions

Step 1: Load State

Step 2: Generate Progress Display

Step 3: Show Phase Dependencies

What this file has done since we first saw it

Other commands, from other repositories

auto-work

develop-review

developing

manual-work

plan-review

analyze