fix: Complete rewrite of progress tracking system (v1.0.9)
The /ab:build command was executing tasks but not tracking progress. This rewrite enforces dual progress tracking in BOTH status.json AND plan.md. Key changes: build.md - Complete restructure: - Step-by-step execution workflow (like migrate.md) - Step 4d MANDATORY: Update both status.json and plan.md - User confirmation required between tasks - Visual Progress Tracker table in plan template planner.md - New plan template: - Progress Tracker table at top with ⬜/✅ indicators - Each task has `- **Status**: ⬜ Pending` field - Status header shows overall progress coder.md - Dual file updates: - 5a: Update status.json (currentTask, tasksCompleted, history) - 5b: Update plan.md Progress Tracker (⬜ Pending → ✅ Done) Benefits: - Visual progress in plan.md (human readable) - JSON progress in status.json (programmatic) - Redundancy ensures progress is never lost - Team can see exactly which tasks are complete 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
38
CHANGELOG.md
38
CHANGELOG.md
@@ -2,6 +2,44 @@
|
||||
|
||||
All notable changes to Auto-Build plugin.
|
||||
|
||||
## [1.0.9] - 2024-12-22
|
||||
|
||||
### Fixed
|
||||
- **Complete rewrite of progress tracking system** - now enforced at every step
|
||||
- Progress is tracked in BOTH status.json AND plan.md (dual tracking)
|
||||
- Plan now includes visual Progress Tracker table with ⬜/✅ status indicators
|
||||
|
||||
### Changed
|
||||
- **build.md**: Complete restructure with step-by-step execution workflow
|
||||
- Step 4d now MANDATORY updates both status.json and plan.md
|
||||
- Added Progress Tracker table format in plan template
|
||||
- User confirmation required between tasks
|
||||
- **planner.md**: New plan.md template with Progress Tracker table
|
||||
- Each task now has `- **Status**: ⬜ Pending` field
|
||||
- Table at top shows all tasks with status columns
|
||||
- **coder.md**: Step 5 now requires updating both files
|
||||
- 5a: Update status.json with currentTask, tasksCompleted
|
||||
- 5b: Update plan.md Progress Tracker (⬜→✅)
|
||||
|
||||
### Why This Matters
|
||||
- Visual progress tracking in plan.md (can see at a glance)
|
||||
- JSON progress in status.json (for programmatic access)
|
||||
- Both files updated = redundancy and visibility
|
||||
- Team members can see exactly which tasks are done
|
||||
|
||||
## [1.0.8] - 2024-12-22
|
||||
|
||||
### Fixed
|
||||
- **`/ab:build` now properly tracks task progress in status.json**
|
||||
- Added explicit "MANDATORY" progress tracking instructions in build.md
|
||||
- Added status.json update step to coder agent
|
||||
- Progress is now visible for team collaboration (currentTask, history entries)
|
||||
|
||||
### Changed
|
||||
- build.md: Added "CRITICAL: Progress Tracking Requirements" section
|
||||
- build.md: Detailed "Step 4c: MANDATORY - Update Progress After Task Completion"
|
||||
- coder.md: New "Step 5: Update Progress (MANDATORY)" before reporting changes
|
||||
|
||||
## [1.0.7] - 2024-12-22
|
||||
|
||||
### Fixed
|
||||
|
||||
Reference in New Issue
Block a user