skills.rest
opendatadiscovery
opendatadiscoveryOFFICIAL
Explore all skills by this author →
WebsiteGitHub

status

Summarize audit and implementation progress from PROGRESS.md and status counts.

Updated Apr 16, 2026
Search Tags:#audit#metrics#reporting#backlog#status#progress-tracking#scanners
One-click install
npx skills add https://github.com/opendatadiscovery/odd-team --skill status-opendatadiscovery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/opendatadiscovery/odd-team/tree/main/.claude/skills/status
Command: npx skills add https://github.com/opendatadiscovery/odd-team --skill status-opendatadiscovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The maintenance system for ODD Team requires real-time visibility into audit progress, backlog workload, and code navigation status.

Core Features & Use Cases

  • Real-time progress overview: scanner completion, backlog item counts, and navigation coverage.
  • Validation and reporting: verify PROGRESS.md matches actual state and surface blockers.
  • Decision support: deliver a concise status snapshot for prioritization and planning.

Quick Start

Read the current system status and display a concise progress summary.

Frequently Asked Questions about status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track audit progress and backlog status at a glance?▼

To track audit progress, this Skill reads state/PROGRESS.md and counts files in findings/ and backlog/ by status, delivering a structured snapshot for prioritization and planning.

How do I generate a status report for code navigation coverage and backlog items?▼

You generate a status report by running the Skill to automatically count backlog items and assess code navigation coverage, surfacing any blockers for immediate decision making.

Can I use this to verify that my audit tracking state matches actual backlog file counts?▼

Yes, you can validate that your audit tracking state matches reality by comparing the recorded PROGRESS.md against the actual files counted in the findings and backlog directories.

Why does my audit progress tracking show mismatched backlog counts?▼

Mismatched backlog counts occur when the recorded state in PROGRESS.md is not synchronized with the actual number of files present in the findings and backlog directories.

What's the best way to surface blockers during an implementation audit?▼

The best way to surface blockers is to generate a structured status snapshot that identifies incomplete scanners and unresolved backlog items for team prioritization.

Related Skills

Explore More Data & Analytics Skills→
Zhow01Zhow01
52

planning-with-files

Coordinate multi-phase tasks using on-disk planning files.

Community
Advanced
elophantoelophanto
116

sprint-prioritization

Generates sprint-ready task lists with optimized schedules and assigned resources from a single project goal.

Community
Intermediate
opendatadiscoveryopendatadiscovery

scan

Run audit scanners against ODD repositories and document findings with Gate 9 citations.

Official
Advanced
ReefBytes-OwnerReefBytes-Owner
1

dashboard

Aggregate agent efficiency metrics from local logs into markdown summaries.

Community
Advanced