Marius Mutu
940c6a9f58
BREAKING CHANGE: Specs, plans, and memory moved from .auto-build-data/ (gitignored) to .auto-build/ (git-tracked) to enable team collaboration. Changes: - Specs/plans now in .auto-build/specs/ (shared with team) - Memory (patterns, gotchas) now in .auto-build/memory/ (shared with team) - .auto-build-data/ now only contains local data (worktrees, cache) - Added /ab:migrate command for existing projects - Removed symlinks from worktree-create.sh (no longer needed) Benefits: - Any developer can continue a plan started by another - Patterns and gotchas shared across team - Works on Windows/Linux/Mac without symlinks - Full version history in git 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
78 lines
2.2 KiB
Markdown
78 lines
2.2 KiB
Markdown
---
|
|
description: Show current Auto-Build status
|
|
---
|
|
|
|
# Auto-Build Status
|
|
|
|
Display the current status of Auto-Build, including active specs and builds.
|
|
|
|
## Workflow
|
|
|
|
1. **Check Data Directory**
|
|
- Verify `.auto-build/` exists
|
|
- If not, create it: `mkdir -p .auto-build/specs .auto-build/memory`
|
|
|
|
2. **List Active Specs**
|
|
- Read all directories in `.auto-build/specs/`
|
|
- For each spec, read `status.json` to get current state
|
|
- Display in table format:
|
|
```
|
|
| Feature | Status | Progress | Last Updated |
|
|
|---------|--------|----------|--------------|
|
|
| user-dashboard | IMPLEMENTING | 3/7 tasks | 2h ago |
|
|
| api-refactor | SPEC_COMPLETE | - | 1d ago |
|
|
```
|
|
|
|
3. **Show Active Worktrees**
|
|
- Read `.auto-build-data/worktrees/worktree-registry.json`
|
|
- Display active worktrees with their paths
|
|
|
|
4. **Memory Summary**
|
|
- Count entries in `.auto-build/memory/patterns.json` and `.auto-build/memory/gotchas.json`
|
|
- Show last update timestamp
|
|
|
|
## Status States
|
|
|
|
| State | Description |
|
|
|-------|-------------|
|
|
| `SPEC_DRAFT` | Specification in progress |
|
|
| `SPEC_COMPLETE` | Specification ready, awaiting build |
|
|
| `PLANNING` | Creating implementation plan |
|
|
| `PLANNING_COMPLETE` | Plan ready, awaiting implementation |
|
|
| `IMPLEMENTING` | Code implementation in progress |
|
|
| `IMPLEMENTATION_COMPLETE` | Code done, awaiting QA |
|
|
| `QA_REVIEW` | QA validation in progress |
|
|
| `QA_FAILED` | QA found issues, needs fixes |
|
|
| `COMPLETE` | Feature fully implemented and validated |
|
|
|
|
## Output Format
|
|
|
|
```
|
|
======================================
|
|
Auto-Build Status
|
|
======================================
|
|
|
|
Active Builds:
|
|
- user-dashboard: IMPLEMENTING (3/7 tasks)
|
|
Worktree: ../ab-worktrees/project-user-dashboard/
|
|
Last update: 2 hours ago
|
|
|
|
- api-refactor: SPEC_COMPLETE
|
|
No worktree
|
|
Last update: 1 day ago
|
|
|
|
Memory:
|
|
- Patterns: 12 entries
|
|
- Gotchas: 5 entries
|
|
- Last updated: 3 days ago
|
|
|
|
Quick Actions:
|
|
- Continue build: /ab:build user-dashboard
|
|
- Start new: /ab:spec "Feature Name"
|
|
```
|
|
|
|
## Edge Cases
|
|
|
|
- If no specs exist: "No active builds. Start with /ab:spec <name>"
|
|
- If data directory missing: Create it automatically
|