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.

Use it to review progress, see work in progress and completed tasks, identify blockers, and determine what should happen next.

It makes the project's current state visible without opening a new work process or manually checking every project document.

progress — Command for Claude Code by 686f6c61/alfred-dev

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/686f6c61/alfred-dev

agentmods

npx agentmods add commands/686f6c61/alfred-dev/progress

Made for: Claude Code.

Or install alfred-dev, the plugin that ships this one along with the rest of its 11 skills, 22 commands, 10 agents, 5 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/686f6c61/alfred-dev/progress/github.svg)](https://agentmods.dev/commands/686f6c61/alfred-dev/progress)

Your own site

<a href="https://agentmods.dev/commands/686f6c61/alfred-dev/progress"><img src="https://agentmods.dev/badge/commands/686f6c61/alfred-dev/progress/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/686f6c61/alfred-dev/progress"><img src="https://agentmods.dev/badge/commands/686f6c61/alfred-dev/progress.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00015	$0.00692
Opus 5.5	$0.00006	$0.00277
Sonnet 5.5	$0.00003	$0.00138
Haiku 4.5	$0.00002	$0.00069

Measured 1mo ago against content hash bf981c375b7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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:

.claude/alfred-dev-state.json
.claude/alfred-handoff.json
.claude/alfred-uat.json
docs/project/progress.md
docs/project/traceability.md
docs/project/kanban/backlog.md
docs/project/kanban/in-progress.md
docs/project/kanban/done.md
docs/project/kanban/blocked.md
docs/project/current.md
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.

1mo 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 (117 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 692 once invoked, about $0.0001 per session on Opus 5.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.

Claude Code Project management ai-agents automation claude-code-plugin sdlc

onboard-dev

Onboard a new developer to the project. Generates personalized onboarding plan, sets up dev environment, creates first tasks, and provides codebase walkthrough.

alphaaiservice/cortex · 29 tokens

octo-schedule

Manage scheduled workflow jobs for the Claude Octopus scheduler.

nyldn/claude-octopus · 24 tokens

octo-scheduler

Manage the Claude Octopus scheduled workflow runner daemon.

nyldn/claude-octopus · 15 tokens

specmanager-build

Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.

joanseg/specmanager · 25 tokens

Read the active sprint’s current status. Refresh stale compilation using grainulator compile --dir or grainulator.compile. Use the resulting nextactions with the user’s current scope and authorization. Output only the two Auto and Manual lists below, with no recap, status counters or offer to continue. Continue useful…

grainulation/grainulator · 0 tokens

dispatcher

Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…

Kanevry/session-orchestrator · 185 tokens