Project Progress Tracker Pro

Problem

Project status often lives in separate updates: front-end, back-end, testing, and design progress may sit in different chats or docs. Owners spend time reassembling numbers, confirming definitions, and missing delays. This skill does not pull data from Jira, Feishu, Notion, or spreadsheets automatically. It turns manually provided progress notes into a review-ready structure.

How It Works

Input can be module name, percentage, due date, or individual task progress. The skill works in these steps:
- Progress aggregation: calculates module completion and overall project progress, using weighted or simple averages
- Plan comparison: checks actual completion against due dates and identifies modules behind schedule
- Risk marking: flags delayed items with ⚠️, then proposes likely causes, impact, and next actions
- Reporting output: generates progress bars, concise table-style text, and a Gantt-chart description that can be pasted into Excel or Feishu

Limits

It fits lightweight weekly reviews, stakeholder updates, cross-module alignment, and pre-retrospective data cleanup. It should not replace a dedicated project management tool. It cannot generate chart files or sync external systems. For complex projects with resource dependencies, task assignment, or capacity planning, use a PM tool and treat this skill as a data-cleanup and reporting draft helper.