bts-statuslisted

# Project Status: Generate/Update Update project status for: $ARGUMENTS If argument is a recipe ID, update status for that recipe only. If argument is "all" or empty, scan all recipes. ## Step 1: Scan Recipes Read `.bts/specs/recipes/` directory: ```bash ls .bts/specs/recipes/ ``` For each recipe directory, read: - `recipe.json` → type, topic, phase - `tasks.json` → implementation progress (if exists) - `test-results.json` → test status (if exists) - `deviation.md` → sync status (if exists) - `review.md` → code review findings (if exists) - `final.md` → spec exists? (if exists) ## Step 2: Determine Recipe States For each recipe, determine its state: | State | Criteria | |-------|----------| | `drafting` | recipe.json exists, no final.md | | `spec` | final.md exists, no tasks.json | | `implementing` | tasks.json exists, some tasks pending | | `implemented` | tasks.json exists, all tasks done | | `tested` | test-results.json exists, status=pass | | `synced` | deviation.md exists | | `complete` | tested + synced | ## Step 3: Generate project-status.md Write to `.bts/specs/project-status.md`: ```markdown # Project Status Updated: {ISO8601} ## Features | Recipe | Type | Topic | State | Tests | Deviations | |--------|------|-------|-------|-------|------------| | r-xxx | blueprint | Auth | complete | 15/15 pass | 0 | | r-yyy | design | API | spec | — | — | ## Architecture ### Implemented Files List all files created/modified across all recipes with tasks.json: ```