Progress Reports Die When Every Git Commit Updates the Kanban Board
1. Why is R&D progress management always so hard?
As a full-stack developer, I've been troubled by one problem for a long time: I write a lot of code, but the progress bar is never accurate.
Common scenarios:
- In the Monday meeting, the project manager asks "How far along is the login module?" I say "Almost done," but it's actually only 60%.
- The task status in ZenTao/Jira is "In Progress," but the exact percentage relies entirely on memory.
- I can't write the weekly report and have to scroll through
git logto recall what I did this week. - When a new requirement PRD comes down, manually breaking it into tasks takes half an hour and it's easy to miss things.
Existing tools are too heavy. Jira's configuration is complex, ZenTao's UI is outdated, and Lark Projects requires switching windows. I wanted something more: a tool that doesn't make me leave the terminal, doesn't add operational burden, and reports progress incidentally when I commit code.
So MaDu was born.
2. What is MaDu?
MaDu = Command Line + Web Platform + AI Assistance
In one sentence: you do a normal git commit in the terminal, MaDu automatically syncs the progress to a web kanban board; manage team tasks on the web board, and AI can also help break down requirements and write daily reports.
Three core concepts:
- Commit is reporting — Doesn't change your existing workflow. When you
git commit, it automatically pops up to let you select a task and progress; once committed, the progress syncs to the platform. - Zero interruption — You can commit even when offline; data is stored locally first and automatically uploaded when back online.
- AI efficiency boost — Upload a PRD document to auto-split tasks, auto-generate commit messages based on
git diff, and organize daily/weekly reports with one click.
3. Core Feature Demo
3.1 CLI: Report progress while committing code
# Initialize project (once)
madu init --base-url http://127.0.0.1:3210
# Then for every subsequent commit
git add .
git commit
The terminal will automatically pop up:
1. Select commit type
2. Select associated task
3. Select task progress
4. Complete commit
The commit message is automatically generated in a standard format:
[TASK-1001] Optimized login page form validation logic (Progress: 70%)
Several UX optimizations:
- Rawlist number selection: No need to scroll up and down with arrow keys; just type the number and press enter.
- Recently used pinned to top: Frequently worked-on tasks always appear first.
- Keyword filtering: When there are more than 15 tasks, type a keyword first to narrow the scope.
- AI-generated commit message: Automatically suggests a commit message based on
git diff; just press enter to use it.
3.2 Quick command shortcuts
# Veterans skip the interaction, one command completes commit + reporting
madu done --task TASK-1001 --progress 70 --type task-iteration -m "Optimized login page form validation logic"
# Fixing a bug works the same way
madu done --bug BUG-1001 --progress 60 -m "Fixed login redirect 404"
3.3 Web Platform: Project Kanban + Member Logs
Open http://127.0.0.1:3210/ and you can see:
- Project list: After expanding each project, it displays tasks, bugs, members, and progress.
- Battery-style progress bar:
<30%red,30-79%blue,≥80%green, clear at a glance. - Member details: Click a member's avatar to view their commit log, daily report, weekly report, and monthly report.
- Token management: Enable/disable token authentication per project to ensure data security.
3.4 AI Smart Task Breakdown
Paste a requirements document, and AI automatically splits it into a structured task list:
It also supports uploading .docx files, automatically extracting the document content into the requirements box:
[Image 7: .docx file upload screenshot]
📸 Screenshot suggestion: Show the process of dragging and dropping a
.docxfile into the requirements box; after upload, display the filename and word count (e.g., "Zhongji Smart Water Platform Software Requirements Specification.docx · 13804 words"), with the extracted plain text content already filled in the text box below.
Check the boxes and create them in the project in one batch.
3.5 AI Organizes Daily/Weekly Reports
Click the "Daily Report" tab on the member details page, and AI automatically generates it based on commit records:
## Daily Report · Zhang San (2026-08-31)
**Completed**
- TASK-1001 User Login Module: Progress increased from 50% to 70%, completed real-time phone number format validation
- BUG-1002 Login Redirect 404: Fixed, verified
**In Progress**
- TASK-1003 Data Statistics Report: Progress 0%, expected to start this week
**Today's Summary**: 2 commits total, fixed 1 bug, advanced 1 task
4. Project Status and Roadmap
Implemented:
- ✅ CLI interactive commit and progress reporting
- ✅ Web platform project/task/bug management
- ✅ Authentication and authorization system (Session + Token)
- ✅ AI smart task breakdown (supports .docx upload)
- ✅ AI auto-generated commit messages
- ✅ AI organized daily/weekly/monthly reports
- ✅ Offline queue and automatic retry upload
- ✅ Recently used tasks pinned to top
- ✅ Assignee assignment and avatar display
- ✅ CLI only pulls tasks assigned to the user
Planned:
- 🚧 Task deadlines + overdue reminders
- 🚧 Estimated vs. actual hours (burndown chart)
- 🚧 Task dependencies (predecessor task blocking)
- 🚧 CI/CD integration (build result write-back)
5. Final Words
MaDu's positioning is not to replace Jira/ZenTao, but to find a balance between "too heavy" and "nothing at all."
For R&D teams of 5-20 people, it's light enough, fast enough, and useful enough. It doesn't change your workflow; it just makes every git commit you do more valuable.
Top 3 of 5 from juejin.cn, machine-translated. The original thread is authoritative.
Comparing with our online practice, the boss's trade-off thinking on weekly reports is very valuable as a reference — bookmarked.
[Fist salute][Fist salute][Fist salute]
Good article, thanks for sharing.
[Fist salute][Fist salute][Fist salute]
First.