speccrew 0.5.19 → 0.6.1

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 (51) hide show
  1. package/.speccrew/agents/speccrew-product-manager.md +2 -1
  2. package/.speccrew/agents/speccrew-system-deployer.md +616 -0
  3. package/.speccrew/agents/speccrew-team-leader.md +7 -3
  4. package/.speccrew/agents/speccrew-test-manager.md +31 -31
  5. package/.speccrew/skills/speccrew-deploy-build/SKILL.md +128 -0
  6. package/.speccrew/skills/speccrew-deploy-migrate/SKILL.md +141 -0
  7. package/.speccrew/skills/speccrew-deploy-smoke-test/SKILL.md +243 -0
  8. package/.speccrew/skills/speccrew-deploy-startup/SKILL.md +218 -0
  9. package/.speccrew/skills/speccrew-dev-backend/SKILL.md +35 -6
  10. package/.speccrew/skills/speccrew-knowledge-techs-generate/templates/CONVENTIONS-DATA-TEMPLATE.md +35 -0
  11. package/.speccrew/skills/speccrew-sd-backend/templates/SD-BACKEND-TEMPLATE.md +6 -3
  12. package/.speccrew/skills/speccrew-test-case-design/SKILL.md +2 -2
  13. package/.speccrew/skills/speccrew-test-code-gen/SKILL.md +2 -2
  14. package/README.ar.md +26 -20
  15. package/README.bn.md +2 -2
  16. package/README.bs.md +21 -15
  17. package/README.da.md +21 -15
  18. package/README.de.md +21 -15
  19. package/README.el.md +2 -2
  20. package/README.en.md +26 -20
  21. package/README.es.md +26 -20
  22. package/README.fr.md +21 -15
  23. package/README.it.md +21 -15
  24. package/README.ja.md +21 -15
  25. package/README.ko.md +21 -15
  26. package/README.md +21 -15
  27. package/README.no.md +21 -15
  28. package/README.pl.md +21 -15
  29. package/README.pt-BR.md +21 -15
  30. package/README.ru.md +21 -15
  31. package/README.th.md +17 -12
  32. package/README.zh-TW.md +21 -15
  33. package/docs/GETTING-STARTED.ar.md +48 -8
  34. package/docs/GETTING-STARTED.bn.md +4 -2
  35. package/docs/GETTING-STARTED.bs.md +4 -2
  36. package/docs/GETTING-STARTED.da.md +48 -8
  37. package/docs/GETTING-STARTED.de.md +50 -8
  38. package/docs/GETTING-STARTED.el.md +42 -6
  39. package/docs/GETTING-STARTED.en.md +48 -8
  40. package/docs/GETTING-STARTED.es.md +48 -8
  41. package/docs/GETTING-STARTED.fr.md +48 -8
  42. package/docs/GETTING-STARTED.it.md +50 -8
  43. package/docs/GETTING-STARTED.ja.md +50 -8
  44. package/docs/GETTING-STARTED.ko.md +50 -8
  45. package/docs/GETTING-STARTED.md +50 -8
  46. package/docs/GETTING-STARTED.no.md +459 -86
  47. package/docs/GETTING-STARTED.th.md +4 -2
  48. package/docs/GETTING-STARTED.zh-TW.md +54 -12
  49. package/package.json +1 -1
  50. package/workspace-template/docs/solutions/agent-knowledge-map.md +4 -3
  51. package/workspace-template/docs/solutions/workspace-structure.md +65 -7
@@ -146,13 +146,15 @@ flowchart LR
146
146
  PRD[Fase 1<br/>Analisi Requisiti<br/>Product Manager] --> FD[Fase 2<br/>Feature Design<br/>Feature Designer]
147
147
  FD --> SD[Fase 3<br/>System Design<br/>System Designer]
148
148
  SD --> DEV[Fase 4<br/>Sviluppo<br/>System Developer]
149
- DEV --> TEST[Fase 5<br/>Test di Sistema<br/>Test Manager]
150
- TEST --> ARCHIVE[Fase 6<br/>Archiviazione]
149
+ DEV --> DEPLOY[Fase 5<br/>Distribuzione<br/>System Deployer]
150
+ DEPLOY --> TEST[Fase 6<br/>Test di Sistema<br/>Test Manager]
151
+ TEST --> ARCHIVE[Fase 7<br/>Archiviazione]
151
152
 
152
153
  KB[(Base di Conoscenza<br/>Per Tutto il Processo)] -.-> PRD
153
154
  KB -.-> FD
154
155
  KB -.-> SD
155
156
  KB -.-> DEV
157
+ KB -.-> DEPLOY
156
158
  KB -.-> TEST
157
159
  ```
158
160
 
@@ -332,7 +334,42 @@ iterations/{iter}/04.development/
332
334
 
333
335
  ---
334
336
 
335
- ### 7.5 Fase 5: Test di Sistema (Test Manager)
337
+ ### 7.5 Fase 5: Distribuzione (System Deployer)
338
+
339
+ **Come Avviare**:
340
+
341
+ ```
342
+ @speccrew-system-deployer avvia distribuzione
343
+ ```
344
+
345
+ **Workflow dell'Agente**:
346
+ 1. Verificare che la fase di sviluppo sia completata (Stage Gate)
347
+ 2. Caricare la base di conoscenza tecnica (configurazione build, configurazione migrazione database, comandi avvio servizi)
348
+ 3. **Checkpoint**: Pre-verifica Ambiente — Verificare strumenti di build, versioni runtime, disponibilità dipendenze
349
+ 4. Eseguire le skill di distribuzione in sequenza: Build → Migrazione Database → Avvio Servizi → Smoke Test
350
+ 5. Emettere rapporto di distribuzione
351
+
352
+ > 💡 **Suggerimento**: Per progetti senza database, il passaggio di migrazione viene saltato automaticamente; per applicazioni client (desktop/mobile), viene utilizzata la modalità di verifica processo invece del controllo salute HTTP.
353
+
354
+ **Deliverable**:
355
+
356
+ ```
357
+ iterations/{iter}/05.deployment/
358
+ ├── {platform-id}/
359
+ │ ├── deployment-plan.md # Piano di distribuzione
360
+ │ └── deployment-log.md # Log esecuzione distribuzione
361
+ └── deployment-report.md # Rapporto distribuzione completata
362
+ ```
363
+
364
+ **Checklist di Conferma**:
365
+ - [ ] Il build è stato completato con successo?
366
+ - [ ] Tutti gli script di migrazione database sono stati eseguiti con successo (se applicabile)?
367
+ - [ ] L'applicazione si avvia normalmente e supera il controllo salute?
368
+ - [ ] Tutti gli smoke test sono passati?
369
+
370
+ ---
371
+
372
+ ### 7.6 Fase 6: Test di Sistema (Test Manager)
336
373
 
337
374
  **Come Avviare**:
338
375
  ```
@@ -349,7 +386,7 @@ iterations/{iter}/04.development/
349
386
 
350
387
  **Deliverable**:
351
388
  ```
352
- iterations/{iter}/05.system-test/
389
+ iterations/{iter}/06.system-test/
353
390
  ├── cases/
354
391
  │ └── {platform-id}/ # Documenti casi di test
355
392
  ├── code/
@@ -367,7 +404,7 @@ iterations/{iter}/05.system-test/
367
404
 
368
405
  ---
369
406
 
370
- ### 7.6 Fase 6: Archiviazione
407
+ ### 7.7 Fase 7: Archiviazione
371
408
 
372
409
  Le iterazioni vengono archiviate automaticamente dopo il completamento:
373
410
 
@@ -378,7 +415,8 @@ speccrew-workspace/iteration-archives/
378
415
  ├── 02.feature-design/
379
416
  ├── 03.system-design/
380
417
  ├── 04.development/
381
- └── 05.system-test/
418
+ ├── 05.deployment/
419
+ └── 06.system-test/
382
420
  ```
383
421
 
384
422
  ---
@@ -469,7 +507,8 @@ Pipeline Status: i001-user-management
469
507
  02 Feature Design: 🔄 In Progress (Checkpoint A passed)
470
508
  03 System Design: ⏳ Pending
471
509
  04 Development: ⏳ Pending
472
- 05 System Test: ⏳ Pending
510
+ 05 Deployment: ⏳ Pending
511
+ 06 System Test: ⏳ Pending
473
512
  ```
474
513
 
475
514
  ### 9.5 Compatibilità all'Indietro
@@ -565,6 +604,7 @@ Dopo l'archiviazione, visualizzare in `speccrew-workspace/iteration-archives/`,
565
604
  | Feature Design | Feature Designer | `@speccrew-feature-designer avvia feature design` |
566
605
  | System Design | System Designer | `@speccrew-system-designer avvia system design` |
567
606
  | Sviluppo | System Developer | `@speccrew-system-developer avvia sviluppo` |
607
+ | Distribuzione | System Deployer | `@speccrew-system-deployer avvia distribuzione` |
568
608
  | Test di Sistema | Test Manager | `@speccrew-test-manager avvia test` |
569
609
 
570
610
  ### Checklist Checkpoint
@@ -575,6 +615,7 @@ Dopo l'archiviazione, visualizzare in `speccrew-workspace/iteration-archives/`,
575
615
  | Feature Design | 1 | Copertura scenari, chiarezza interazione, completezza dati, gestione eccezioni |
576
616
  | System Design | 2 | A: Valutazione framework; B: Sintassi pseudocodice, consistenza cross-piattaforma, gestione errori |
577
617
  | Sviluppo | 1 | A: Pronto ambiente, problemi integrazione, specifiche codice |
618
+ | Distribuzione | 1 | Build riuscito, migrazione completata, servizi avviati, smoke test passati |
578
619
  | Test di Sistema | 2 | A: Copertura casi; B: Eseguibilità codice test |
579
620
 
580
621
  ### Riferimento Rapido Percorsi Deliverable
@@ -585,7 +626,8 @@ Dopo l'archiviazione, visualizzare in `speccrew-workspace/iteration-archives/`,
585
626
  | Feature Design | `iterations/{iter}/02.feature-design/` | `[name]-feature-spec.md` |
586
627
  | System Design | `iterations/{iter}/03.system-design/` | `DESIGN-OVERVIEW.md`, `{platform}/INDEX.md`, `{platform}/{module}-design.md` |
587
628
  | Sviluppo | `iterations/{iter}/04.development/` | Codice sorgente + `delivery-report.md` |
588
- | Test di Sistema | `iterations/{iter}/05.system-test/` | `cases/`, `code/`, `reports/`, `bugs/` |
629
+ | Distribuzione | `iterations/{iter}/05.deployment/` | `deployment-plan.md`, `deployment-log.md`, `deployment-report.md` |
630
+ | Test di Sistema | `iterations/{iter}/06.system-test/` | `cases/`, `code/`, `reports/`, `bugs/` |
589
631
  | Archiviazione | `iteration-archives/{iter}-{date}/` | Copia completa dell'iterazione |
590
632
 
591
633
  ---
@@ -146,13 +146,15 @@ flowchart LR
146
146
  PRD[フェーズ1<br/>要件分析<br/>Product Manager] --> FD[フェーズ2<br/>機能設計<br/>Feature Designer]
147
147
  FD --> SD[フェーズ3<br/>システム設計<br/>System Designer]
148
148
  SD --> DEV[フェーズ4<br/>開発実装<br/>System Developer]
149
- DEV --> TEST[フェーズ5<br/>システムテスト<br/>Test Manager]
150
- TEST --> ARCHIVE[フェーズ6<br/>アーカイブ]
149
+ DEV --> DEPLOY[フェーズ5<br/>デプロイ実施<br/>System Deployer]
150
+ DEPLOY --> TEST[フェーズ6<br/>システムテスト<br/>Test Manager]
151
+ TEST --> ARCHIVE[フェーズ7<br/>アーカイブ]
151
152
 
152
153
  KB[(ナレッジベース<br/>全体を通して)] -.-> PRD
153
154
  KB -.-> FD
154
155
  KB -.-> SD
155
156
  KB -.-> DEV
157
+ KB -.-> DEPLOY
156
158
  KB -.-> TEST
157
159
  ```
158
160
 
@@ -332,7 +334,42 @@ iterations/{iter}/04.development/
332
334
 
333
335
  ---
334
336
 
335
- ### 7.5 フェーズ5:システムテスト(Test Manager)
337
+ ### 7.5 フェーズ5:デプロイ実施(System Deployer)
338
+
339
+ **開始方法**:
340
+
341
+ ```
342
+ @speccrew-system-deployer デプロイを開始
343
+ ```
344
+
345
+ **エージェントワークフロー**:
346
+ 1. 開発フェーズが完了したことを検証(Stage Gate)
347
+ 2. テクニカルナレッジベースをロード(ビルド構成、データベースマイグレーション構成、サービス起動コマンド)
348
+ 3. **チェックポイント**:環境プレチェック — ビルドツール、ランタイムバージョン、依存関係の可用性を検証
349
+ 4. 順番にデプロイスキルを実行:ビルド(Build)→ データベースマイグレーション(Migrate)→ サービス起動(Startup)→ スモークテスト(Smoke Test)
350
+ 5. デプロイレポートを出力
351
+
352
+ > 💡 **ヒント**:データベースのないプロジェクトの場合、マイグレーションステップは自動的にスキップされます。クライアントアプリケーション(デスクトップ/モバイル)の場合、HTTPヘルスチェックの代わりにプロセス検証モードが使用されます。
353
+
354
+ **成果物**:
355
+
356
+ ```
357
+ iterations/{iter}/05.deployment/
358
+ ├── {platform-id}/
359
+ │ ├── deployment-plan.md # デプロイ計画
360
+ │ └── deployment-log.md # デプロイ実行ログ
361
+ └── deployment-report.md # デプロイ完了レポート
362
+ ```
363
+
364
+ **確認ポイント**:
365
+ - [ ] ビルドが正常に完了したか
366
+ - [ ] データベースマイグレーションスクリプトがすべて正常に実行されたか(該当する場合)
367
+ - [ ] アプリケーションが正常に起動しヘルスチェックに合格したか
368
+ - [ ] スモークテストがすべて合格したか
369
+
370
+ ---
371
+
372
+ ### 7.6 フェーズ6:システムテスト(Test Manager)
336
373
 
337
374
  **開始方法**:
338
375
  ```
@@ -349,7 +386,7 @@ iterations/{iter}/04.development/
349
386
 
350
387
  **成果物**:
351
388
  ```
352
- iterations/{iter}/05.system-test/
389
+ iterations/{iter}/06.system-test/
353
390
  ├── cases/
354
391
  │ └── {platform-id}/ # テストケースドキュメント
355
392
  ├── code/
@@ -367,7 +404,7 @@ iterations/{iter}/05.system-test/
367
404
 
368
405
  ---
369
406
 
370
- ### 7.6 フェーズ6:アーカイブ
407
+ ### 7.7 フェーズ7:アーカイブ
371
408
 
372
409
  イテレーション完了後自動的にアーカイブ:
373
410
 
@@ -378,7 +415,8 @@ speccrew-workspace/iteration-archives/
378
415
  ├── 02.feature-design/
379
416
  ├── 03.system-design/
380
417
  ├── 04.development/
381
- └── 05.system-test/
418
+ ├── 05.deployment/
419
+ └── 06.system-test/
382
420
  ```
383
421
 
384
422
  ---
@@ -469,7 +507,8 @@ Pipeline Status: i001-user-management
469
507
  02 Feature Design: 🔄 In Progress (Checkpoint A passed)
470
508
  03 System Design: ⏳ Pending
471
509
  04 Development: ⏳ Pending
472
- 05 System Test: ⏳ Pending
510
+ 05 Deployment: ⏳ Pending
511
+ 06 System Test: ⏳ Pending
473
512
  ```
474
513
 
475
514
  ### 9.5 下位互換性
@@ -565,6 +604,7 @@ npm install -g speccrew@0.5.6
565
604
  | 機能設計 | Feature Designer | `@speccrew-feature-designer 機能設計を開始` |
566
605
  | システム設計 | System Designer | `@speccrew-system-designer システム設計を開始` |
567
606
  | 開発 | System Developer | `@speccrew-system-developer 開発を開始` |
607
+ | デプロイ | System Deployer | `@speccrew-system-deployer デプロイを開始` |
568
608
  | システムテスト | Test Manager | `@speccrew-test-manager テストを開始` |
569
609
 
570
610
  ### チェックポイントチェックリスト
@@ -575,6 +615,7 @@ npm install -g speccrew@0.5.6
575
615
  | 機能設計 | 1 | シナリオカバレッジ、インタラクションの明確さ、データの完全性、例外処理 |
576
616
  | システム設計 | 2 | A: フレームワーク評価; B: 擬似コード構文、クロスプラットフォーム一貫性、エラー処理 |
577
617
  | 開発 | 1 | A: 環境の準備、統合問題、コード規約 |
618
+ | デプロイ | 1 | ビルド成功、マイグレーション完了、サービス起動、スモークテスト合格 |
578
619
  | システムテスト | 2 | A: ケースカバレッジ; B: テストコードの実行可能性 |
579
620
 
580
621
  ### 成果物パスクイックリファレンス
@@ -585,7 +626,8 @@ npm install -g speccrew@0.5.6
585
626
  | 機能設計 | `iterations/{iter}/02.feature-design/` | `[name]-feature-spec.md` |
586
627
  | システム設計 | `iterations/{iter}/03.system-design/` | `DESIGN-OVERVIEW.md`, `{platform}/INDEX.md`, `{platform}/{module}-design.md` |
587
628
  | 開発 | `iterations/{iter}/04.development/` | ソースコード + `delivery-report.md` |
588
- | システムテスト | `iterations/{iter}/05.system-test/` | `cases/`, `code/`, `reports/`, `bugs/` |
629
+ | デプロイ | `iterations/{iter}/05.deployment/` | `deployment-plan.md`, `deployment-log.md`, `deployment-report.md` |
630
+ | システムテスト | `iterations/{iter}/06.system-test/` | `cases/`, `code/`, `reports/`, `bugs/` |
589
631
  | アーカイブ | `iteration-archives/{iter}-{date}/` | 完全なイテレーションコピー |
590
632
 
591
633
  ---
@@ -146,13 +146,15 @@ flowchart LR
146
146
  PRD[1단계<br/>요구사항 분석<br/>Product Manager] --> FD[2단계<br/>기능 설계<br/>Feature Designer]
147
147
  FD --> SD[3단계<br/>시스템 설계<br/>System Designer]
148
148
  SD --> DEV[4단계<br/>개발 구현<br/>System Developer]
149
- DEV --> TEST[5단계<br/>시스템 테스트<br/>Test Manager]
150
- TEST --> ARCHIVE[6단계<br/>보관]
149
+ DEV --> DEPLOY[5단계<br/>배포 실행<br/>System Deployer]
150
+ DEPLOY --> TEST[6단계<br/>시스템 테스트<br/>Test Manager]
151
+ TEST --> ARCHIVE[7단계<br/>보관]
151
152
 
152
153
  KB[(지식 기반<br/>전체 과정)] -.-> PRD
153
154
  KB -.-> FD
154
155
  KB -.-> SD
155
156
  KB -.-> DEV
157
+ KB -.-> DEPLOY
156
158
  KB -.-> TEST
157
159
  ```
158
160
 
@@ -332,7 +334,42 @@ iterations/{iter}/04.development/
332
334
 
333
335
  ---
334
336
 
335
- ### 7.5 5단계: 시스템 테스트 (Test Manager)
337
+ ### 7.5 5단계: 배포 실행 (System Deployer)
338
+
339
+ **시작 방법**:
340
+
341
+ ```
342
+ @speccrew-system-deployer 배포 시작
343
+ ```
344
+
345
+ **Agent 워크플로우**:
346
+ 1. 개발 단계 완료 검증 (Stage Gate)
347
+ 2. 기술 지식 기반 로드 (빌드 구성, 데이터베이스 마이그레이션 구성, 서비스 시작 명령)
348
+ 3. **체크포인트**: 환경 사전 검사 — 빌드 도구, 런타임 버전, 종속성 가용성 검증
349
+ 4. 순차적으로 배포 스킬 실행: 빌드(Build) → 데이터베이스 마이그레이션(Migrate) → 서비스 시작(Startup) → 스모크 테스트(Smoke Test)
350
+ 5. 배포 보고서 출력
351
+
352
+ > 💡 **팁**: 데이터베이스가 없는 프로젝트의 경우 마이그레이션 단계는 자동으로 건너뜁니다. 클라이언트 애플리케이션(데스크톱/모바일)의 경우 HTTP 헬스 체크 대신 프로세스 검증 모드를 사용합니다.
353
+
354
+ **산출물**:
355
+
356
+ ```
357
+ iterations/{iter}/05.deployment/
358
+ ├── {platform-id}/
359
+ │ ├── deployment-plan.md # 배포 계획
360
+ │ └── deployment-log.md # 배포 실행 로그
361
+ └── deployment-report.md # 배포 완료 보고서
362
+ ```
363
+
364
+ **확인 체크리스트**:
365
+ - [ ] 빌드가 정상적으로 완료되었는가
366
+ - [ ] 데이터베이스 마이그레이션 스크립트가 모두 정상 실행되었는가 (해당하는 경우)
367
+ - [ ] 애플리케이션이 정상적으로 시작되고 헬스 체크를 통과했는가
368
+ - [ ] 스모크 테스트가 모두 통과했는가
369
+
370
+ ---
371
+
372
+ ### 7.6 6단계: 시스템 테스트 (Test Manager)
336
373
 
337
374
  **시작 방법**:
338
375
  ```
@@ -349,7 +386,7 @@ iterations/{iter}/04.development/
349
386
 
350
387
  **산출물**:
351
388
  ```
352
- iterations/{iter}/05.system-test/
389
+ iterations/{iter}/06.system-test/
353
390
  ├── cases/
354
391
  │ └── {platform-id}/ # 테스트 케이스 문서
355
392
  ├── code/
@@ -367,7 +404,7 @@ iterations/{iter}/05.system-test/
367
404
 
368
405
  ---
369
406
 
370
- ### 7.6 6단계: 보관
407
+ ### 7.7 7단계: 보관
371
408
 
372
409
  반복 완료 후 자동 보관:
373
410
 
@@ -378,7 +415,8 @@ speccrew-workspace/iteration-archives/
378
415
  ├── 02.feature-design/
379
416
  ├── 03.system-design/
380
417
  ├── 04.development/
381
- └── 05.system-test/
418
+ ├── 05.deployment/
419
+ └── 06.system-test/
382
420
  ```
383
421
 
384
422
  ---
@@ -469,7 +507,8 @@ Pipeline Status: i001-user-management
469
507
  02 Feature Design: 🔄 In Progress (Checkpoint A passed)
470
508
  03 System Design: ⏳ Pending
471
509
  04 Development: ⏳ Pending
472
- 05 System Test: ⏳ Pending
510
+ 05 Deployment: ⏳ Pending
511
+ 06 System Test: ⏳ Pending
473
512
  ```
474
513
 
475
514
  ### 9.5 하위 호환성
@@ -565,6 +604,7 @@ npm install -g speccrew@0.5.6
565
604
  | 기능 설계 | Feature Designer | `@speccrew-feature-designer 기능 설계 시작` |
566
605
  | 시스템 설계 | System Designer | `@speccrew-system-designer 시스템 설계 시작` |
567
606
  | 개발 | System Developer | `@speccrew-system-developer 개발 시작` |
607
+ | 배포 | System Deployer | `@speccrew-system-deployer 배포 시작` |
568
608
  | 시스템 테스트 | Test Manager | `@speccrew-test-manager 테스트 시작` |
569
609
 
570
610
  ### 체크포인트 체크리스트
@@ -575,6 +615,7 @@ npm install -g speccrew@0.5.6
575
615
  | 기능 설계 | 1 | 시나리오 커버리지, 상호작용 명확성, 데이터 완전성, 예외 처리 |
576
616
  | 시스템 설계 | 2 | A: 프레임워크 평가; B: 의사코드 구문, 크로스플랫폼 일관성, 오류 처리 |
577
617
  | 개발 | 1 | A: 환경 준비, 통합 문제, 코드 규약 |
618
+ | 배포 | 1 | 빌드 성공, 마이그레이션 완료, 서비스 시작, 스모크 테스트 통과 |
578
619
  | 시스템 테스트 | 2 | A: 케이스 커버리지; B: 테스트 코드 실행 가능성 |
579
620
 
580
621
  ### 산출물 경로 빠른 참조
@@ -585,7 +626,8 @@ npm install -g speccrew@0.5.6
585
626
  | 기능 설계 | `iterations/{iter}/02.feature-design/` | `[name]-feature-spec.md` |
586
627
  | 시스템 설계 | `iterations/{iter}/03.system-design/` | `DESIGN-OVERVIEW.md`, `{platform}/INDEX.md`, `{platform}/{module}-design.md` |
587
628
  | 개발 | `iterations/{iter}/04.development/` | 소스 코드 + `delivery-report.md` |
588
- | 시스템 테스트 | `iterations/{iter}/05.system-test/` | `cases/`, `code/`, `reports/`, `bugs/` |
629
+ | 배포 | `iterations/{iter}/05.deployment/` | `deployment-plan.md`, `deployment-log.md`, `deployment-report.md` |
630
+ | 시스템 테스트 | `iterations/{iter}/06.system-test/` | `cases/`, `code/`, `reports/`, `bugs/` |
589
631
  | 보관 | `iteration-archives/{iter}-{date}/` | 전체 반복 복사본 |
590
632
 
591
633
  ---
@@ -146,13 +146,15 @@ flowchart LR
146
146
  PRD[阶段一<br/>需求分析<br/>Product Manager] --> FD[阶段二<br/>功能设计<br/>Feature Designer]
147
147
  FD --> SD[阶段三<br/>系统设计<br/>System Designer]
148
148
  SD --> DEV[阶段四<br/>开发实现<br/>System Developer]
149
- DEV --> TEST[阶段五<br/>系统测试<br/>Test Manager]
150
- TEST --> ARCHIVE[阶段六<br/>归档]
149
+ DEV --> DEPLOY[阶段五<br/>部署实施<br/>System Deployer]
150
+ DEPLOY --> TEST[阶段六<br/>系统测试<br/>Test Manager]
151
+ TEST --> ARCHIVE[阶段七<br/>归档]
151
152
 
152
153
  KB[(知识库<br/>贯穿始终)] -.-> PRD
153
154
  KB -.-> FD
154
155
  KB -.-> SD
155
156
  KB -.-> DEV
157
+ KB -.-> DEPLOY
156
158
  KB -.-> TEST
157
159
  ```
158
160
 
@@ -332,7 +334,42 @@ iterations/{iter}/04.development/
332
334
 
333
335
  ---
334
336
 
335
- ### 7.5 阶段五:系统测试(Test Manager
337
+ ### 7.5 阶段五:部署实施(System Deployer
338
+
339
+ **如何启动**:
340
+
341
+ ```
342
+ @speccrew-system-deployer 开始部署
343
+ ```
344
+
345
+ **Agent 工作流程**:
346
+ 1. 验证开发阶段已完成(Stage Gate)
347
+ 2. 加载技术知识库(构建配置、数据库迁移配置、服务启动命令)
348
+ 3. **Checkpoint**:环境预检 — 验证构建工具、运行时版本、依赖可用性
349
+ 4. 按顺序执行部署技能:构建(Build)→ 数据库迁移(Migrate)→ 服务启动(Startup)→ 烟雾测试(Smoke Test)
350
+ 5. 输出部署报告
351
+
352
+ > 💡 **提示**:对于无数据库的项目,迁移步骤会自动跳过;对于客户端应用(桌面/移动端),会使用进程验证模式替代 HTTP 健康检查。
353
+
354
+ **产出物**:
355
+
356
+ ```
357
+ iterations/{iter}/05.deployment/
358
+ ├── {platform-id}/
359
+ │ ├── deployment-plan.md # 部署计划
360
+ │ └── deployment-log.md # 部署执行日志
361
+ └── deployment-report.md # 部署完成报告
362
+ ```
363
+
364
+ **确认要点**:
365
+ - [ ] 构建是否成功完成
366
+ - [ ] 数据库迁移脚本是否全部执行成功(如适用)
367
+ - [ ] 应用是否正常启动并通过健康检查
368
+ - [ ] 烟雾测试是否全部通过
369
+
370
+ ---
371
+
372
+ ### 7.6 阶段六:系统测试(Test Manager)
336
373
 
337
374
  **如何启动**:
338
375
  ```
@@ -349,7 +386,7 @@ iterations/{iter}/04.development/
349
386
 
350
387
  **产出物**:
351
388
  ```
352
- iterations/{iter}/05.system-test/
389
+ iterations/{iter}/06.system-test/
353
390
  ├── cases/
354
391
  │ └── {platform-id}/ # 测试用例文档
355
392
  ├── code/
@@ -367,7 +404,7 @@ iterations/{iter}/05.system-test/
367
404
 
368
405
  ---
369
406
 
370
- ### 7.6 阶段六:归档
407
+ ### 7.7 阶段七:归档
371
408
 
372
409
  迭代完成后自动归档:
373
410
 
@@ -378,7 +415,8 @@ speccrew-workspace/iteration-archives/
378
415
  ├── 02.feature-design/
379
416
  ├── 03.system-design/
380
417
  ├── 04.development/
381
- └── 05.system-test/
418
+ ├── 05.deployment/
419
+ └── 06.system-test/
382
420
  ```
383
421
 
384
422
  ---
@@ -469,7 +507,8 @@ Pipeline Status: i001-user-management
469
507
  02 Feature Design: 🔄 In Progress (Checkpoint A passed)
470
508
  03 System Design: ⏳ Pending
471
509
  04 Development: ⏳ Pending
472
- 05 System Test: ⏳ Pending
510
+ 05 Deployment: ⏳ Pending
511
+ 06 System Test: ⏳ Pending
473
512
  ```
474
513
 
475
514
  ### 9.5 向下兼容
@@ -565,6 +604,7 @@ npm install -g speccrew@0.5.6
565
604
  | 功能设计 | Feature Designer | `@speccrew-feature-designer 开始功能设计` |
566
605
  | 系统设计 | System Designer | `@speccrew-system-designer 开始系统设计` |
567
606
  | 开发实现 | System Developer | `@speccrew-system-developer 开始开发` |
607
+ | 部署实施 | System Deployer | `@speccrew-system-deployer 开始部署` |
568
608
  | 系统测试 | Test Manager | `@speccrew-test-manager 开始测试` |
569
609
 
570
610
  ### Checkpoint 检查清单
@@ -575,6 +615,7 @@ npm install -g speccrew@0.5.6
575
615
  | 功能设计 | 1 | 场景覆盖、交互清晰度、数据完整性、异常处理 |
576
616
  | 系统设计 | 2 | A: 框架评估;B: 伪代码语法、跨端一致性、错误处理 |
577
617
  | 开发实现 | 1 | A: 环境就绪、集成问题、代码规约 |
618
+ | 部署实施 | 1 | 构建成功、迁移完成、服务启动、烟雾测试通过 |
578
619
  | 系统测试 | 2 | A: 用例覆盖;B: 测试代码可运行性 |
579
620
 
580
621
  ### 产出物路径速查
@@ -585,7 +626,8 @@ npm install -g speccrew@0.5.6
585
626
  | 功能设计 | `iterations/{iter}/02.feature-design/` | `[name]-feature-spec.md` |
586
627
  | 系统设计 | `iterations/{iter}/03.system-design/` | `DESIGN-OVERVIEW.md`, `{platform}/INDEX.md`, `{platform}/{module}-design.md` |
587
628
  | 开发实现 | `iterations/{iter}/04.development/` | 源代码 + `delivery-report.md` |
588
- | 系统测试 | `iterations/{iter}/05.system-test/` | `cases/`, `code/`, `reports/`, `bugs/` |
629
+ | 部署实施 | `iterations/{iter}/05.deployment/` | `deployment-plan.md`, `deployment-log.md`, `deployment-report.md` |
630
+ | 系统测试 | `iterations/{iter}/06.system-test/` | `cases/`, `code/`, `reports/`, `bugs/` |
589
631
  | 归档 | `iteration-archives/{iter}-{date}/` | 完整迭代副本 |
590
632
 
591
633
  ---