Summarize current project state from Backlog.md (task counts, in-progress work, milestones) and point to the Project Dashboard. Use when the user asks for status, progress, or a project overview.
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add adam-s-k-i/super-backlog --skill backlog-status-report --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Backlog Status Report?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/adam-s-k-i-backlog-status-report-super-backlog)More formats (shields.io, HTML) on the badges page.
---
name: backlog-status-report
description: Summarize current project state from Backlog.md (task counts, in-progress work, milestones) and point to the Project Dashboard. Use when the user asks for status, progress, or a project overview.
---
<!-- managed-by: super-backlog 1.3.1 -->
# Backlog Status Report: project state at a glance
Read-only summary of the Backlog.md data in this project.
## When this skill runs
- The user asks for status, progress, or an overview ("where are we?").
- Before or after a work session, to orient.
## Procedure
1. Read `backlog instructions overview` if not already loaded this session.
2. Collect data: `backlog task list --json` plus milestones via the backlog CLI.
3. Report compactly in chat:
- Counts per status (To Do / In Progress / Done)
- Every In Progress task: ID, title, open acceptance criteria
- Milestones with done/total
- Blocked or stale items worth flagging
4. Point to the visual surfaces: `sbl dashboard` (live dashboard) or
`backlog browser` (interactive Kanban).
## Boundaries
- Strictly read-only: never change task status, never edit tasks.
- Never guess state from memory — always read fresh CLI output.
- Keep the report short; link details instead of pasting them.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
