status

Aggregate tasks, milestones, and progress logs into a status report.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/azadmotala/claude-code-team-builder --skill status-azadmotala
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/azadmotala/claude-code-team-builder/tree/main/examples/saas-dashboard/.claude/skills/status
Command: npx skills add https://github.com/azadmotala/claude-code-team-builder --skill status-azadmotala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reports the current state of a software project for TenantFlow, showing what is done, what's in progress, what's blocked, and what remains next.

Core Features & Use Cases

  • State aggregation: loads and aggregates data from tasks.json and orchestrator_state.json to compute milestone progress and task status.
  • Status categories: classifies tasks as Done, In progress, Blocked, Pending, or Failed for clear visibility.
  • Activity and failures: surfaces recent activity from progress.log and highlights any failed tasks with retry history.
  • Actionable output: presents the next actions and overall health in a concise, console-friendly format.

Quick Start

Run the status command at any time to view the latest project health, milestones, and next actions.

Frequently Asked Questions about status

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

FAQPage Schema
How do I generate a project status report from tasks.json and orchestrator_state.json?

Generate a project status report by reading tasks.json, orchestrator_state.json, and progress.log to aggregate milestone progress and classify task states like Done, In progress, Blocked, or Failed.

Can I track milestone progress and task status from a progress log file?

Track milestone progress and task status by parsing progress.log to surface recent activity and highlight failed tasks with retry history alongside data loaded from tasks.json.

What's the best way to see blocked and pending tasks in a software project?

See blocked and pending tasks by aggregating project state from orchestrator_state.json and tasks.json, which classifies tasks into clear status categories for immediate visibility.

Does project status reporting work without an orchestrator_state.json file?

Project status reporting requires read access to tasks.json, orchestrator_state.json, and progress.log to compute state and present results, so the orchestrator state file is a necessary dependency.

How do I surface failed tasks and retry history for a project management workflow?

Surface failed tasks and retry history by analyzing progress.log entries, which extracts failure events and pairs them with current task classifications from tasks.json.

Why does my project status summary show missing milestone data?

Project status summaries show missing milestone data when tasks.json or orchestrator_state.json lack proper task definitions or milestone mappings required to compute grouped progress.