progress-report
/progress-report
Report progress against the current plan in plain English: on track or not, done, running, blocked, needs you, next. Use for /progress-report.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.
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-report.
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-report.
How it works
SKILL.md has no level-two headings · 18 lines, 151 words
SKILL.md preview
--- name: progress-report description: "Report progress against the current plan in plain English: on track or not, done, running, blocked, needs you, next. Use for /progress-report." disable-model-invocation: true --- # Progress report 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.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · caidanw/skills | 86 | MIT |
| samykabu/sanduq-skills | 90 | MIT |
| krishp147/skills | 90 | MIT |
Database snapshot: 13.11.2026 · package version 1d94e4d443d1 (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 progress against the current plan in plain English: on track or not, done, running, blocked, needs you, next. Use for /progress. - 100report-progress
Writes a progress report from the status template, or from a template the project added. Use it when someone asks for a status report, a progress update, or a report template of their own. - 100generate-status-report
Generate a project status report from live Orangescrum data: progress, completed and open work, overdue items, the active sprint, and time logged. When an agent needs to: (1) Write a weekly or sprint status update, (2) Summarize progress for stakeholders, (3) List overdue or… - 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. - 86report-writer
Write a weekly progress report from the repository's recent activity. Use when the user asks for a progress report, a weekly report, or a status write-up.