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:
@@ -68,13 +68,62 @@ After coding:
|
||||
- Verify changes match completion criteria
|
||||
- Ensure no unintended side effects
|
||||
|
||||
### 5. Report Changes
|
||||
### 5. Update Progress (MANDATORY)
|
||||
|
||||
**After completing the task, you MUST update BOTH files:**
|
||||
|
||||
#### 5a. Update status.json
|
||||
|
||||
Read and update `.auto-build/specs/{feature-name}/status.json`:
|
||||
```json
|
||||
{
|
||||
"status": "IMPLEMENTING",
|
||||
"currentTask": {N+1},
|
||||
"tasksCompleted": {N},
|
||||
"totalTasks": {TOTAL},
|
||||
"updated": "{ISO timestamp}",
|
||||
"history": [
|
||||
...existing...,
|
||||
{"status": "IMPLEMENTING", "at": "{timestamp}", "task": {N}, "title": "{title}", "completed": true}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
#### 5b. Update plan.md Progress Tracker
|
||||
|
||||
Edit `.auto-build/specs/{feature-name}/plan.md` to mark task complete:
|
||||
|
||||
1. In the Progress Tracker table, change:
|
||||
```
|
||||
| {N} | {Task title} | ⬜ Pending | |
|
||||
```
|
||||
to:
|
||||
```
|
||||
| {N} | {Task title} | ✅ Done | {timestamp} |
|
||||
```
|
||||
|
||||
2. In the task section, change:
|
||||
```
|
||||
- **Status**: ⬜ Pending
|
||||
```
|
||||
to:
|
||||
```
|
||||
- **Status**: ✅ Done ({timestamp})
|
||||
```
|
||||
|
||||
**Both updates are MANDATORY. Skipping them breaks team collaboration and progress tracking.**
|
||||
|
||||
### 6. Report Changes
|
||||
|
||||
Provide a summary:
|
||||
|
||||
```markdown
|
||||
## Task Completed: [Task Title]
|
||||
|
||||
### Progress Updated
|
||||
- status.json updated: currentTask = {N+1}
|
||||
- History entry added for task {N}
|
||||
|
||||
### Changes Made
|
||||
|
||||
#### `path/to/file1.ts`
|
||||
|
||||
@@ -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...]
|
||||
|
||||
Reference in New Issue
Block a user