Skip to content
Skills Library
Management & product · Planning

progress

/progress

Report progress against the current plan in plain English: on track or not, done, running, blocked, needs you, next. Use for /progress.

Repository
skills ↗
Licence
MIT
Last repository change
19.10.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Report progress against the current plan in plain English: on track or not, done, running, blocked, needs you, next. Use for /progress.

Original author description

Report progress against the current plan in plain English: on track or not, done, running, blocked, needs you, next. Use for /progress.

How it works

SKILL.md has no level-two headings · 18 lines, 150 words

SKILL.md preview
---
name: progress
description: "Report progress against the current plan in plain English: on track or not, done, running, blocked, needs you, next. Use for /progress."
disable-model-invocation: true
---

# Progress

Report where the work stands against its plan, then keep working.

1. Find the plan: the day-plan file, a plan file, the todos, or the ticket. Without one, measure against the goal the user stated.
2. Check live state before you write anything: running jobs, each subagent (working, stuck, or waiting on you), PRs and CI, and the newest results files. Answer any subagent that is waiting on you first.
3. Reply in plain English, under 150 words:
   - One line: on track or not, and why.
   - Done since the last report.
   - Running now, each with an honest ETA or "unknown".
   - Blocked, and what unblocks it.
   - What needs the user, each item with your recommendation.
   - The next step you will take.
4. Continue the work unless the user told you to stop.

**Done when:** every line is checked against live state, not memory.
Files in this package (2)
  • SKILL.md 1 KB
  • progress-report/SKILL.md 1 KB

Versions

RepositoryScoreLicence
This page · caidanw/skills86MIT
Embassy-of-the-Free-Mind/sourcelibrary-v2100AGPL-3.0
builderio/agent-native100MIT
olehsov/gcp-certification-coach100MIT
M-reza-kd/lead-flow-plugin100MIT
yarikleto/claude-teacher-plugin100MIT
avsm/ocaml-claude-marketplace100ISC
maludb/learn-claude100MIT
matteocervelli/llms100MIT

Database snapshot: 13.11.2026 · package version 34bf843dea94 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 86progress-report
    Report progress against the current plan in plain English: on track or not, done, running, blocked, needs you, next. Use for /progress-report.
  • 100task-progress
    Report Noisy Studio task progress, delegated work, blockers and explicit review artifacts through its MCP tools. Use while doing multi-step work when report_task and list_tasks are available, or when the user requests dashboard progress reporting.
  • 100progress-tracking
    Validates feature plans, tracks implementation progress, and verifies code-level requirements traceability. Use when validating a feature plan, tracking its progress, or checking requirements against code.
  • 100work-summary
    Generates a project dashboard from MCP work items. Default is a lean, attention-first view: what's in flight, what's blocked, what to do next, what's queued. Use when the user says: project status, what's active, show me the dashboard, work summary, what should I work on,…
  • 86relay-board
    Show the relay revision queue as a board — what is in progress, what is next, what waits for proof or an answer, what is blocked and what is done. Use when the user types /relay-board or asks what is in progress or done in the queue.
  • 100project-dashboard
    This skill should be used when users ask 'where am I?', 'what is my progress?', mentions 'status', 'dashboard', 'progress', wants to know if they are ready for the next stage, or needs an overview of their project state.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.