romfast/auto-build
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: Complete rewrite of progress tracking system (v1.0.9)

Browse Source 
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:
Marius Mutu
2025-12-22 21:20:48 +02:00
parent e8a371d0a3
commit 6dc644d9fb
6 changed files with 357 additions and 186 deletions
Download Patch File Download Diff File Expand all files Collapse all files

76
plugin/agents/planner.md
View File

@@ -66,56 +66,54 @@ Create a plan.md with this structure:
```markdown
# Implementation Plan: {feature-name}
**Status**: 🔄 In Progress
**Created**: {timestamp}
**Total Tasks**: {N}
## Progress Tracker
| # | Task | Status | Completed |
|---|------|--------|-----------|
| 1 | {Task 1 title} | ⬜ Pending | |
| 2 | {Task 2 title} | ⬜ Pending | |
| 3 | {Task 3 title} | ⬜ Pending | |
| ... | ... | ... | |
## Overview
[Brief summary of the implementation approach]
## Task Order
1. Task 1 (no dependencies)
2. Task 2 (depends on 1)
3. Task 3 (depends on 1)
4. Task 4 (depends on 2, 3)
...
## Detailed Tasks
## Tasks
---
### Task 1: [Clear Title]
**Objective**: [One sentence describing what this task accomplishes]
**Files**:
- `path/to/file1.ts` - [what to do]
- `path/to/file2.ts` - [what to do]
**Steps**:
1. [Specific step 1]
2. [Specific step 2]
3. [Specific step 3]
**Dependencies**: None
**Completion Criteria**:
- [ ] [How to verify this task is done]
**Patterns to Follow**:
- See `existing/similar/file.ts` for reference
- **Status**: ⬜ Pending
- **Objective**: [One sentence describing what this task accomplishes]
- **Files**:
- `path/to/file1.ts` - [what to do]
- `path/to/file2.ts` - [what to do]
- **Steps**:
1. [Specific step 1]
2. [Specific step 2]
3. [Specific step 3]
- **Dependencies**: None
- **Completion Criteria**:
- [ ] [How to verify this task is done]
---
### Task 2: [Clear Title]
**Objective**: [One sentence]
**Files**:
- `path/to/file3.ts` - [what to do]
**Steps**:
1. [Specific step 1]
2. [Specific step 2]
**Dependencies**: Task 1
**Completion Criteria**:
- [ ] [Verification method]
- **Status**: ⬜ Pending
- **Objective**: [One sentence]
- **Files**:
- `path/to/file3.ts` - [what to do]
- **Steps**:
1. [Specific step 1]
2. [Specific step 2]
- **Dependencies**: Task 1
- **Completion Criteria**:
- [ ] [Verification method]
---
[Continue for all tasks...]