project-status

Analyze SE artifacts and tickets to generate a structured project status report.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/busboom-software-studio/design-trainer --skill project-status-busboom-software-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-status
Source: https://github.com/busboom-software-studio/design-trainer/tree/main/.claude/skills/project-status
Command: npx skills add https://github.com/busboom-software-studio/design-trainer --skill project-status-busboom-software-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes SE artifacts and tickets to determine project state and outline the next actions.

Core Features & Use Cases

  • Reads docs/clasi/design, sprints, and tickets to determine project stage.
  • Reports progress with artifact status, active sprint, ticket counts, and blockers.
  • Recommends next actions based on current stage and blockers.

Quick Start

Provide the repository's artifacts and tickets to generate a current project status report.

Frequently Asked Questions about project-status

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

FAQPage Schema
How do I generate a project status report from tickets and design docs?

To generate a project status report, provide your repository's software engineering artifacts, sprint data, and tickets. The tool analyzes these inputs to output a structured report covering project stage, blockers, and next actions.

What is the best way to track sprint progress and identify blockers automatically?

Tracking sprint progress and identifying blockers is done by reading sprint data and ticket tracking systems. It evaluates ticket counts and artifact status to pinpoint current project blockers and recommend actionable next steps.

Can I analyze project health if my team uses custom design documents?

Yes, you can analyze project health with custom design documents. The analysis applies to projects with docs, sprints, and ticket tracking, reading the specific design artifacts to determine the current project stage.

How do project status reports determine next actions for development teams?

Project status reports determine next actions by analyzing the current project stage alongside identified blockers. It reads your design documents, active sprints, and tickets to recommend the most relevant steps forward.

Do I need a specific ticket management system to analyze project state?

No specific ticket management system is required, but you need exportable ticket data and sprint records. The analysis applies to any project with accessible docs, sprints, and ticket tracking to determine the state.

Why does my project status report show no active sprint or blockers?

A project status report shows no active sprint or blockers when the provided tickets and sprint data are empty or unreadable. Ensure your repository contains updated sprint folders and ticket tracking artifacts for accurate analysis.