Marius Mutu
6dc644d9fb
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>
114 lines
4.1 KiB
Markdown
114 lines
4.1 KiB
Markdown
# Changelog
|
|
|
|
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
|
|
- Improved `/ab:migrate` command with clearer execution instructions
|
|
- Changed migration from `mv` to `cp` for safer data preservation
|
|
- Added explicit "Execute These Steps Immediately" section for Claude
|
|
|
|
## [1.0.6] - 2024-12-22
|
|
|
|
### Changed (BREAKING)
|
|
- **Specs and plans moved to `.auto-build/`** (git-tracked) for multi-developer collaboration
|
|
- **Memory moved to `.auto-build/memory/`** (git-tracked) so team shares learned patterns
|
|
- `.auto-build-data/` now only contains local data (worktrees, cache)
|
|
|
|
### Added
|
|
- New `/ab:migrate` command for existing projects to migrate from old structure
|
|
- Documentation updates explaining git-tracked vs local data separation
|
|
|
|
### Removed
|
|
- Symlinks in worktree-create.sh - no longer needed since data is in git
|
|
- Old `.auto-build-data/specs/` and `.auto-build-data/memory/` paths
|
|
|
|
### Benefits
|
|
- 🤝 Multi-developer collaboration - any developer can continue a plan
|
|
- 🧠 Shared learning - patterns and gotchas available to entire team
|
|
- 🌍 Cross-platform - works on Windows/Linux/Mac without symlinks
|
|
- 📜 Version history - specs/plans/memory changes visible in git
|
|
|
|
## [1.0.5] - 2024-12-22
|
|
|
|
### Fixed
|
|
- Worktree now creates symlinks to `.auto-build-data/` and `.claude/rules/` from main repo
|
|
- This ensures specs, plans, status, and memory are shared across worktrees
|
|
- `/ab:build` in worktree will correctly detect `PLANNING_COMPLETE` status and continue
|
|
|
|
### Improved
|
|
- Clarified in build.md that `PLANNING_COMPLETE` skips planning phase
|
|
|
|
## [1.0.4] - 2024-12-22
|
|
|
|
### Improved
|
|
- Clear "ACTION REQUIRED" message after worktree creation
|
|
- Explicit next steps showing user must open new VSCode window in worktree
|
|
- Explains why switching is necessary (Claude Code sessions are directory-bound)
|
|
|
|
## [1.0.3] - 2024-12-22
|
|
|
|
### Fixed
|
|
- Worktree scripts now use `$(pwd)` for project root instead of calculating from script location
|
|
- Scripts work correctly when called via `${CLAUDE_PLUGIN_ROOT}/scripts/`
|
|
|
|
## [1.0.2] - 2024-12-21
|
|
|
|
### Added
|
|
- CLAUDE.md file for development guidance
|
|
|
|
## [1.0.1] - 2024-12-21
|
|
|
|
### Fixed
|
|
- hooks.json format corrected (use object instead of array)
|
|
|
|
## [1.0.0] - 2024-12-20
|
|
|
|
### Added
|
|
- Initial release
|
|
- 8 commands: spec, build, worktree, qa-review, memory-save, memory-search, status, help
|
|
- 5 agents: spec-writer, planner, coder, qa-reviewer, qa-fixer
|
|
- Git worktree isolation support
|
|
- Bidirectional memory system (JSON + Markdown)
|
|
- CLAUDE.md integration with context-aware agents
|
|
- Post-install hook for automatic setup
|