progress

A project-status command that summarises current progress, task-board items, blockers, and traceability for a software project. It uses the project's existing status records to show the next operational step.

In plain words
What is it for?
Use it to review progress, see work in progress and completed tasks, identify blockers, and determine what should happen next.
Why use it?
It makes the project's current state visible without opening a new work process or manually checking every project document.

Command

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/686f6c61/alfred-dev/progress
Clone the repo
git clone --depth 1 https://github.com/686f6c61/alfred-dev
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 692 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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00692
Opus 5 $0.00008 $0.00346
Sonnet 5 $0.00003 $0.00138
Haiku 4.5 $0.00002 $0.00069

Measured 2d ago against content hash bf981c375b7c, 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 2d ago.

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.

commands/progress.md · 70 lines

How it starts

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

/alfred-dev:progress

Eres Alfred. Tu trabajo aquí es hacer visible el estado operativo que SonIA y el proyecto ya tienen, no abrir un flujo nuevo.

Protocolo

Paso único por defecto: este comando es un wrapper del helper determinista. No empieces explorando el repo ni leyendo artefactos uno a uno. Ejecuta este Bash inmediatamente y usa su stdout como base de tu respuesta final:

python3 .claude/alfred-continuity.py progress "$PWD"

Después de ejecutar el Bash:

  • si el helper devuelve un resumen válido, úsalo como respuesta final y no sigas explorando ni lo reenvuelvas con otra capa de progreso;
  • trata focus, source, command, directive y reason como la guía canónica del siguiente paso;
  • si el helper falla, entonces sí puedes entrar en modo manual.

Solo si el helper falla o no está disponible, cae al modo manual y entonces lee en este orden, si existen:

  1. .claude/alfred-dev-state.json
  2. .claude/alfred-handoff.json
  3. .claude/alfred-uat.json
  4. docs/project/progress.md
  5. docs/project/traceability.md
  6. docs/project/kanban/backlog.md
  7. docs/project/kanban/in-progress.md
  8. docs/project/kanban/done.md
  9. docs/project/kanban/blocked.md
  10. docs/project/current.md
  11. docs/project/discovery.md

Qué debes mostrar

Presenta un resumen breve y accionable con estas secciones:

  • estado del flujo activo o del handoff si existe;
  • progreso general del proyecto según docs/project/progress.md;
  • trabajo en curso y trabajo bloqueado según el kanban;
  • huecos de trazabilidad visibles en docs/project/traceability.md;
  • estado de UAT si existe;
  • siguiente comando recomendado.

Reglas

  • NO uses Read, Glob, Grep ni otras herramientas de exploración antes de intentar el Bash del helper.
  • Si el helper ya ha devuelto un resumen útil, NO añadas insights especulativos sobre instalación del plugin, registro del comando o estado del entorno.
  • Si no hay sesión activa pero sí artefactos de SonIA, trátalos como la fuente principal del estado del proyecto.
  • NO reabras el flujo activo ni intentes superar gates desde /alfred-dev:progress.
  • Si faltan algunos artefactos, dilo claramente y trabaja con lo que sí exista.
  • Si no existe nada en docs/project/, sugiere el paso correcto: /alfred-dev:map-codebase, /alfred-dev:feature, /alfred-dev:quick, /alfred-dev:fix, /alfred-dev:spike o /alfred-dev:audit.
  • No conviertas esto en un informe largo ni decorativo; tiene que servir para decidir qué toca ahora.
  • NO uses AskUserQuestion como paso obligatorio dentro de /alfred-dev:progress.

Read the full file on GitHub · 70 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.

  1. 2d ago First seen · 70 lines · 15 tokens per session scan A bf981c375b7c

Subscribe to this mod's changes

progress is a command published in the GitHub repository 686f6c61/alfred-dev (119 stars, last pushed 17d ago), licensed MIT. It adds 15 tokens to every session and 692 once invoked, about $0.0001 per session on Opus 5. 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-30.