buildcrew 1.3.1 → 1.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/agents/buildcrew.md +102 -9
  2. package/package.json +1 -1
@@ -167,22 +167,27 @@ Automated release — test, version, changelog, push, PR.
167
167
 
168
168
  ## Workflow: Feature Mode
169
169
 
170
+ Each iteration runs the **full end-to-end pipeline**. The planner re-evaluates at the start of every cycle.
171
+
170
172
  ```
171
173
  [Feature Request]
172
174
 
173
175
 
176
+ ━━━ Iteration 1/N ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
177
+
178
+
174
179
  ┌─────────┐
175
- │ PLANNER │ → Requirements & acceptance criteria
176
- └────┬────┘
180
+ │ PLANNER │ → Iteration 1: full requirements & acceptance criteria
181
+ └────┬────┘ Iteration 2+: review previous cycle results, refine plan
177
182
 
178
183
 
179
184
  ┌──────────┐
180
- │ DESIGNER │ → UI spec + HTML prototype
181
- └────┬─────┘
185
+ │ DESIGNER │ → Iteration 1: full UI/UX research + components
186
+ └────┬─────┘ Iteration 2+: refine based on QA/review feedback
182
187
 
183
188
 
184
189
  ┌───────────┐
185
- │ DEVELOPER │ → Implementation
190
+ │ DEVELOPER │ → Implement / fix / improve
186
191
  └────┬──────┘
187
192
 
188
193
 
@@ -201,13 +206,25 @@ Automated release — test, version, changelog, push, PR.
201
206
  └────┬───────┘
202
207
 
203
208
 
204
- [Quality Gate: All PASS?]
209
+ [All PASS + no improvements left?]
205
210
 
206
- No │──→ Back to relevant phase (iteration +1)
211
+ No │──→ Next iteration (full pipeline from PLANNER)
207
212
 
208
213
  Yes │──→ ✅ Complete (suggest Ship Mode)
214
+ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
209
215
  ```
210
216
 
217
+ ### Iteration Behavior by Agent
218
+
219
+ | Agent | Iteration 1 | Iteration 2+ |
220
+ |-------|------------|--------------|
221
+ | **Planner** | Full requirements analysis | Reviews QA/review findings, updates acceptance criteria, identifies new improvement areas |
222
+ | **Designer** | Full research + components | Refines UI based on feedback, fixes design issues found in QA |
223
+ | **Developer** | Full implementation | Fixes issues, implements improvements from updated plan |
224
+ | **QA Tester** | Full verification | Re-verifies fixes + regression check |
225
+ | **Browser QA** | Full browser testing | Re-tests affected flows + new issues |
226
+ | **Reviewer** | Full code review | Verifies fixes applied correctly, new review pass |
227
+
211
228
  **Note**: Browser QA is skipped for non-UI features (API-only, config changes, etc.). Reviewer always runs.
212
229
 
213
230
  ## Workflow: Project Audit Mode
@@ -453,6 +470,74 @@ Output: `.claude/pipeline/project-audit/00-backlog.md` with prioritized issue li
453
470
 
454
471
  ---
455
472
 
473
+ ## Status Log (Required)
474
+
475
+ You MUST output a structured status log **before and after** every agent dispatch. This is how the user tracks pipeline progress in real time.
476
+
477
+ ### Format
478
+
479
+ ```
480
+ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
481
+ buildcrew · Feature: {feature-name}
482
+ Mode: Feature · Iteration: 1/3
483
+ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
484
+
485
+ [1/6] PLANNER ·················· requirements analysis
486
+ [2/6] DESIGNER ················· UI/UX research + components
487
+ [3/6] DEVELOPER ················ implementation
488
+ [4/6] QA TESTER ················ code verification
489
+ [5/6] BROWSER QA ··············· real browser testing
490
+ [6/6] REVIEWER ················· code review + auto-fix
491
+ ```
492
+
493
+ ### Before dispatching an agent
494
+
495
+ ```
496
+ ▶ PLANNER · Starting requirements analysis...
497
+ ```
498
+
499
+ ### After an agent completes
500
+
501
+ ```
502
+ ✓ PLANNER · Done → 01-plan.md (3 user stories, 12 acceptance criteria)
503
+ ▶ DESIGNER · Starting UI/UX research...
504
+ ```
505
+
506
+ ### On iteration (full cycle restart)
507
+
508
+ ```
509
+ ✗ REVIEWER · 3 issues found (perf regression, missing error state, a11y)
510
+ ↻ Starting iteration 2/5 — full pipeline from PLANNER
511
+ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
512
+ buildcrew · Feature: {feature-name}
513
+ Mode: Feature · Iteration: 2/5
514
+ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
515
+ ▶ PLANNER · Reviewing iteration 1 results, updating plan...
516
+ ```
517
+
518
+ ### On completion
519
+
520
+ ```
521
+ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
522
+ ✓ COMPLETE · {feature-name}
523
+ Pipeline: planner → designer → developer → qa → reviewer
524
+ Iterations: 2
525
+ Output: .claude/pipeline/{feature-name}/
526
+ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
527
+ ```
528
+
529
+ ### Rules for Status Log
530
+
531
+ 1. **Always output the header** at the start of every mode execution — shows mode, feature name, max iterations, and full agent pipeline
532
+ 2. **Always log before dispatch** — `▶ AGENT · Starting [task]...`
533
+ 3. **Always log after completion** — `✓ AGENT · Done → [output file] ([brief summary])`
534
+ 4. **Always log failures** — `✗ AGENT · [issue count] issues found ([brief description])`
535
+ 5. **Always log iterations** — `↻ AGENT · Fixing issues (iteration N/M)...`
536
+ 6. **Keep summaries to one line** — the detail is in the pipeline docs, the log is for quick scanning
537
+ 7. **Show the pipeline overview at the start** — numbered list of all agents that will run, so the user knows what's coming
538
+
539
+ ---
540
+
456
541
  ## Rules
457
542
 
458
543
  ### 1. Handoff Protocol
@@ -504,8 +589,16 @@ Each agent's output follows this structure:
504
589
  1. Parse feature request and iteration count (default: 3)
505
590
  2. Create pipeline directory: `.claude/pipeline/{feature-name}/`
506
591
  3. Create tasks for tracking progress
507
- 4. Run **planner** **designer** **developer** **qa-tester** **browser-qa** (if UI) → **reviewer**
508
- 5. All PASS suggest Ship Mode, FAIL route back, iterate
592
+ 4. **For each iteration (1 to N), run the FULL pipeline:**
593
+ - **planner**reviews previous cycle results (iteration 2+), updates plan
594
+ - **designer** → refines UI based on feedback (iteration 2+)
595
+ - **developer** → implements / fixes / improves
596
+ - **qa-tester** → verifies code-level quality
597
+ - **browser-qa** (if UI) → real browser testing
598
+ - **reviewer** → code review + auto-fix
599
+ 5. All PASS + no improvements left → suggest Ship Mode
600
+ 6. Issues remain → next full iteration from PLANNER
601
+ 7. **Every iteration is a complete end-to-end cycle, not a partial fix loop**
509
602
 
510
603
  ### Project Audit Mode
511
604
  1. Create pipeline directory: `.claude/pipeline/project-audit/`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "buildcrew",
3
- "version": "1.3.1",
3
+ "version": "1.4.0",
4
4
  "description": "11 AI agents for Claude Code — auto-orchestrated dev team with 9 operating modes",
5
5
  "homepage": "https://buildcrew-landing.vercel.app",
6
6
  "author": "z1nun",