tracking-progress

Analyze project progress from git logs, test results, and architectural data.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/k2works/claude-code-booster --skill tracking-progress
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tracking-progress
Source: https://github.com/k2works/claude-code-booster/tree/main/lib/assets/.claude/skills/tracking-progress
Command: npx skills add https://github.com/k2works/claude-code-booster --skill tracking-progress

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

プロジェクト開発の進捗を包括的に分析し、イテレーション達成度・技術実装状況・品質メトリクスをレポートとして提供します。進捗の透明性を高め、利害関係者への報告を効率化します。

Core Features & Use Cases

  • イテレーションの達成度とスプリントの進捗を自動で集計
  • 技術実装状況と品質メトリクスを統合して可視化
  • 進捗データをドキュメントへ反映し、リリース計画や振り返りを支援

Quick Start

最新の変更を取り込み、現在の進捗レポートを生成して共有してください。

Frequently Asked Questions about tracking-progress

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

FAQPage Schema
How do I automate project progress reporting from git logs and test results?

Automate project progress reporting by analyzing git logs, test results, and architectural progress to evaluate iteration completion and quality metrics. This consolidates findings into structured reports for milestones and stakeholder communications without manual data gathering.

What is the best way to track iteration progress and technical status for stakeholder reporting?

Track iteration progress by evaluating iteration completion, technical implementation status, and quality metrics. The process consolidates these findings into structured reports suitable for milestone reviews and stakeholder communications.

Can I generate quality metrics and iteration progress reports for software projects of varying sizes?

Yes, you can generate progress reports for software projects of varying sizes. The analysis applies to iteration progress, technical status, and quality metrics, producing automated checks on status and trends for stakeholder reporting.

How do I integrate progress data into documentation for release planning and retrospectives?

Integrate progress data into documentation by automating data collection from git logs and test results, then consolidating findings into structured reports. This supports optional documentation updates to aid release planning and retrospectives.

Do I need any specific dependencies to analyze technical implementation status and quality metrics?

No specific dependencies are required to analyze technical implementation status and quality metrics. The skill operates independently to collect data from git logs and test results, consolidating findings into structured progress reports.