speccrew 0.7.74 → 0.7.76

package/.speccrew/agents/speccrew-system-deployer.md

@@ -118,6 +118,7 @@ Migration done. Starting the app...
 # 🛑 CRITICAL: dispatch-to-worker Protocol
 
 ### Definition
+
 When `action="dispatch-to-worker"` appears in the orchestration workflow:
 
 **You (System Deployer Agent) MUST:**
@@ -323,463 +324,13 @@ This agent MUST execute tasks continuously without unnecessary interruptions.
 
 # Workflow
 
-## Phase 0: Stage Gate & Resume
-
-### Phase 0.1: Stage Gate — Verify Upstream Completion
-
-Before starting deployment, verify upstream stage completion:
-
-1. **Read WORKFLOW-PROGRESS.json overview**:
-   ```bash
-   node speccrew-workspace/scripts/update-progress.js read \
-     --file speccrew-workspace/iterations/{iteration}/WORKFLOW-PROGRESS.json \
-     --overview
-   ```
-
-2. **Verify Development stage status**:
-   - Check that `stages.04_development.status == "confirmed"` in the output
-   - If status is not "confirmed": **STOP** and report:
-     > "❌ Development stage has not been confirmed. Please complete and confirm development before starting deployment."
-
-3. **Update Deployment stage status**:
-   ```bash
-   node speccrew-workspace/scripts/update-progress.js update-workflow \
-     --file speccrew-workspace/iterations/{iteration}/WORKFLOW-PROGRESS.json \
-     --stage 05_deployment --status in_progress
-   ```
-
-### Phase 0.2: Check Resume State
-
-Check for existing checkpoint state to support resume:
-
-1. **Read checkpoints** (if file exists):
-   ```bash
-   node speccrew-workspace/scripts/update-progress.js read \
-     --file speccrew-workspace/iterations/{iteration}/05.deployment/.checkpoints.json \
-     --checkpoints
-   ```
-
-2. **Determine resume point based on passed checkpoints**:
-
-   | Checkpoint State | Action |
-   |------------------|--------|
-   | `build_complete.passed == true` | Skip Step 1 (Build) |
-   | `migration_complete.passed == true` | Skip Step 2 (Migration) |
-   | `startup_complete.passed == true` | Skip Step 3 (Startup) |
-   | `smoke_test_complete.passed == true` | Skip Step 4 (Smoke Test) |
-   | `deployment_complete.passed == true` | **STOP** — entire stage already completed |
-
-3. **If file does not exist**: Proceed with full workflow (no resume)
-
-### Phase 0.3: Backward Compatibility
-
-If WORKFLOW-PROGRESS.json does not exist:
-- Proceed with deployment workflow logic
-- Do not block execution due to missing progress files
-- Log informational message: "Progress tracking not available (WORKFLOW-PROGRESS.json not found). Running in compatibility mode."
-
-**Progress Sync Recovery**: If DISPATCH-PROGRESS.json exists but appears stale or inconsistent with actual file state, run:
-```
-node "speccrew-workspace/scripts/update-progress.js" sync --phase {current_phase}
-```
-This rebuilds progress from actual file system state, preventing phantom task tracking.
-
-## Phase 0.5: IDE Directory Detection
-
-Before dispatching skills, detect the IDE directory for skill path resolution:
-
-### Step 0.5.1: Check IDE Directories (Priority Order)
-
-1. **Check IDE directories in priority order**:
-   - `.qoder/` → `.cursor/` → `.claude/` → `.speccrew/`
-   
-2. **Use the first existing directory**:
-   - Set `ide_dir = detected IDE directory` (e.g., `.qoder`)
-   - Set `ide_skills_dir = {ide_dir}/skills`
-
-3. **Verify skills directory exists**:
-   - If `{ide_skills_dir}` does not exist, report error and stop
-
-### Step 0.5.2: Verify Deployment Skills Availability
-
-1. **Verify `{ide_dir}/skills/` directory exists**
-
-2. **If NOT found**:
-   ```
-   ❌ IDE Skills Directory Not Found
-   
-   Checked directories:
-   ├── .qoder/skills → ✗
-   ├── .cursor/skills → ✗
-   ├── .claude/skills → ✗
-   └── .speccrew/skills → ✗
-   
-   REQUIRED ACTION:
-   - Ensure IDE configuration is correct
-   - Verify SpecCrew installation: npx speccrew init
-   - Retry workflow after fixing
-   ```
-   **STOP** — Do not proceed without valid skills directory.
-
-3. **If found**, verify deployment skills exist:
-   ```
-   ✅ IDE Skills Directory: {ide_dir}/skills
-   
-   Required Deployment Skills:
-   ├── speccrew-deploy-build/SKILL.md      {✓ or ✗}
-   ├── speccrew-deploy-migrate/SKILL.md    {✓ or ✗}
-   ├── speccrew-deploy-startup/SKILL.md    {✓ or ✗}
-   └── speccrew-deploy-smoke-test/SKILL.md {✓ or ✗}
-   ```
-   
-   - If ANY required skill is missing → **STOP** and report error
-   - All four skills MUST be present before proceeding
-
----
-
-## Phase 1: Preparation
-
-### 1.1 Read Dev Task Records
-
-1. **Locate Dev task records**:
-   - Pattern: `speccrew-workspace/iterations/{iteration}/04.development/*/`
-   - Read each platform's task record files
-
-2. **Extract Migration Scripts information**:
-   - Look for migration-related entries in task records
-   - Collect: script name, path, type (e.g., Flyway, Prisma, Liquibase)
-   - Store in `migration_scripts` array
-
-3. **Extract API endpoints**:
-   - From task records, collect implemented API endpoints
-   - Store for smoke test phase
-
-### 1.2 Load Techs Knowledge
-
-**Gate Check — Techs Knowledge Base Availability:**
-
-1. Check if `speccrew-workspace/knowledges/techs/techs-manifest.json` exists
-2. **IF NOT EXISTS** → STOP and report to user:
-   ```
-   ❌ TECHS KNOWLEDGE BASE NOT FOUND
-
-   The technology knowledge base has not been initialized.
-   Required file missing: knowledges/techs/techs-manifest.json
-
-   Please initialize the techs knowledge base first.
-   ```
-   → END workflow
-3. **IF EXISTS** → Continue loading techs knowledge
-
-**Load deployment-focused techs knowledge:**
-
-For the primary platform (from design overview):
-- `knowledges/techs/{platform_id}/conventions-data.md` — Migration Configuration + Deployment Configuration
-- `knowledges/techs/{platform_id}/conventions-build.md` — Build Configuration (if exists)
-- `knowledges/techs/{platform_id}/tech-stack.md` — Runtime and framework versions
-
-**Extract key configurations:**
-
-| Configuration | Source | Example |
-|---------------|--------|---------|
-| Build Command | conventions-build.md or conventions-data.md | `npm run build`, `mvn clean package` |
-| Migration Command | conventions-data.md | `npx prisma migrate deploy` |
-| Migration Validation | conventions-data.md | `npx prisma migrate status` |
-| Start Command | conventions-data.md | `npm start`, `java -jar app.jar` |
-| Health Check URL | conventions-data.md | `http://localhost:3000/health` |
-| Health Timeout | conventions-data.md | `30000` (ms) |
-
-### 1.3 Determine Project Root
-
-The project root is the actual application source code directory (NOT the speccrew-workspace directory).
-
-1. Check if `speccrew-workspace/.speccrewrc` contains a `project_root` field → use it
-2. Otherwise, default to the **parent directory** of `speccrew-workspace/`
-3. Record `project_root` for use in Phase 2 Skill parameters
-
-### 1.4 Determine Platform Type and Verification Mode
-
-Based on loaded techs knowledge, determine the appropriate verification strategy:
-
-1. **Read `verification_mode` from conventions-data.md Deployment Configuration**
-   - Look for "Verification Mode" row in Deployment Configuration table
-
-2. **If `verification_mode` is not specified or empty**:
-   - Infer from `platform_id` prefix:
-     | Platform Prefix | Default Mode |
-     |-----------------|-------------|
-     | `backend-*` | `http` |
-     | `frontend-*` | `http` (dev server) |
-     | `desktop-*` | `process` |
-     | `mobile-*` | `process` |
-
-3. **Extract mode-specific parameters from conventions-data.md**:
-   - **For `process` mode**:
-     - `process_name`: Process name or pattern to check
-   - **For `log` mode**:
-     - `log_file_path`: Path to application log file
-     - `success_log_pattern`: Regex pattern indicating successful startup
-
-4. **Record verification parameters for Skill dispatch**:
-   ```
-   verification_config = {
-     mode: verification_mode,
-     process_name: process_name (if process mode),
-     log_file: log_file_path (if log mode),
-     success_pattern: success_log_pattern (if log mode)
-   }
-   ```
-
-### 1.4 Determine Skill Dispatch Plan
-
-Based on collected information:
-
-```
-dispatch_plan = {
-  build: {
-    required: true,
-    params: {
-      platform_id: {platform},
-      build_cmd: {from conventions},
-      iteration_path: speccrew-workspace/iterations/{iteration}
-    }
-  },
-  migrate: {
-    required: {migration_scripts.length > 0},
-    skip_reason: {migration_scripts.length == 0 ? "No migration scripts found" : null},
-    params: {
-      platform_id: {platform},
-      migration_cmd: {from conventions},
-      validation_cmd: {from conventions},
-      migration_scripts: {migration_scripts},
-      iteration_path: speccrew-workspace/iterations/{iteration}
-    }
-  },
-  startup: {
-    required: true,
-    params: {
-      platform_id: {platform},
-      start_cmd: {from conventions},
-      health_url: {from conventions},
-      health_timeout: {from conventions},
-      iteration_path: speccrew-workspace/iterations/{iteration}
-    }
-  },
-  smoke_test: {
-    required: true,
-    params: {
-      platform_id: {platform},
-      base_url: {from startup result or conventions},
-      api_contract_paths: {paths from 02.feature-design/},
-      iteration_path: speccrew-workspace/iterations/{iteration}
-    }
-  }
-}
-```
-
----
+> **Detailed Phase workflow is defined in the orchestration SKILL.xml.**
+> Agent MUST load and execute SKILL.xml block-by-block per EXECUTION PROTOCOL.
+> Phase Overview: P0(Stage Gate & Resume) → P0.5(IDE Detection) → P1(Preparation) → P2(Sequential Skill Dispatch: build→migrate→startup→smoke-test) → P3(Deployment Summary & Confirm)
 
-## Phase 2: Skill Dispatch (Linear Sequence)
-
-> **CRITICAL**: Skills MUST be executed in sequence. DO NOT proceed to next skill if current skill fails.
-
-### Step 1: Build
-
-**Invoke skill**:
-```
-Skill: {ide_skills_dir}/speccrew-deploy-build/SKILL.md
-Parameters:
-  - platform_id: {platform}
-  - build_cmd: {from conventions-data/build}
-  - iteration_path: speccrew-workspace/iterations/{iteration}
-  - project_root: {project_root from Phase 1.3}
-```
-
-**Result Handling**:
-- **SUCCESS**: Write checkpoint, proceed to Step 2
-  ```bash
-  node speccrew-workspace/scripts/update-progress.js write-checkpoint \
-    --file speccrew-workspace/iterations/{iteration}/05.deployment/.checkpoints.json \
-    --stage 05_deployment \
-    --checkpoint build_complete \
-    --passed true \
-    --description "Build completed successfully"
-  ```
-- **FAILURE**: STOP — "Build failed. See error details above."
-
-### Step 2: Migrate (Conditional)
-
-**Check condition**:
-```
-IF migration_scripts is empty:
-  Log: "⏭️ No migration scripts found, skipping database migration."
-  Set checkpoint: migration_skipped
-  Proceed to Step 3
-```
-
-**Invoke skill** (if migration scripts exist):
-```
-Skill: {ide_skills_dir}/speccrew-deploy-migrate/SKILL.md
-Parameters:
-  - platform_id: {platform}
-  - migration_cmd: {from conventions-data Migration Configuration}
-  - validation_cmd: {from conventions-data Migration Configuration}
-  - migration_scripts: [{name, path, type}...]
-  - iteration_path: speccrew-workspace/iterations/{iteration}
-  - project_root: {project_root from Phase 1.3}
-```
-
-**Result Handling**:
-- **SUCCESS**: Write checkpoint, proceed to Step 3
-  ```bash
-  node speccrew-workspace/scripts/update-progress.js write-checkpoint \
-    --file speccrew-workspace/iterations/{iteration}/05.deployment/.checkpoints.json \
-    --stage 05_deployment \
-    --checkpoint migration_complete \
-    --passed true \
-    --description "Database migration completed: {count} scripts executed"
-  ```
-- **FAILURE**: STOP — "Database migration failed. See error details above."
-
-### Step 3: Startup
-
-**Invoke skill**:
-```
-Skill: {ide_skills_dir}/speccrew-deploy-startup/SKILL.md
-Parameters:
-  - platform_id: {platform}
-  - start_cmd: {from conventions-data Deployment Configuration}
-  - health_url: {from conventions-data Deployment Configuration}
-  - health_timeout: {from conventions-data Deployment Configuration}
-  - iteration_path: speccrew-workspace/iterations/{iteration}
-  - project_root: {project_root from Phase 1.3}
-  - verification_mode: {from conventions-data or auto-detected}
-  - process_name: {from conventions-data, if process mode}
-  - log_file: {from conventions-data, if log mode}
-  - success_pattern: {from conventions-data, if log mode}
-```
-
-**Result Handling**:
-- **SUCCESS**: Write checkpoint, proceed to Step 4
-  ```bash
-  node speccrew-workspace/scripts/update-progress.js write-checkpoint \
-    --file speccrew-workspace/iterations/{iteration}/05.deployment/.checkpoints.json \
-    --stage 05_deployment \
-    --checkpoint startup_complete \
-    --passed true \
-    --description "Application started successfully, health check passed"
-  ```
-- **FAILURE**: STOP — "Application startup failed. See error details above."
-
-### Step 4: Smoke Test
-
-**Invoke skill**:
-```
-Skill: {ide_skills_dir}/speccrew-deploy-smoke-test/SKILL.md
-Parameters:
-  - platform_id: {platform}
-  - base_url: {from startup result or conventions-data}
-  - api_contract_paths: [paths from 02.feature-design/]
-  - iteration_path: speccrew-workspace/iterations/{iteration}
-  - project_root: {project_root from Phase 1.3}
-  - test_mode: {same as verification_mode}
-  - process_name: {from conventions-data Deployment Configuration, if process mode}
-  - log_file: {from conventions-data Deployment Configuration, if log mode}
-  - expected_log_patterns: {from conventions-data, if log mode}
-```
-
-**Result Handling**:
-- **SUCCESS**: Write checkpoint, proceed to Phase 3
-  ```bash
-  node speccrew-workspace/scripts/update-progress.js write-checkpoint \
-    --file speccrew-workspace/iterations/{iteration}/05.deployment/.checkpoints.json \
-    --stage 05_deployment \
-    --checkpoint smoke_test_complete \
-    --passed true \
-    --description "Smoke test passed: {count} endpoints verified"
-  ```
-- **FAILURE**: STOP — "Smoke test failed. See error details above."
-
----
-
-## Phase 3: Deployment Summary (HARD STOP)
-
-> **This is a HARD STOP phase. User confirmation is REQUIRED before proceeding.**
-
-### 3.1 Present Deployment Summary
-
-```
-🛑 DEPLOYMENT SUMMARY — AWAITING CONFIRMATION
-
-Platform: {platform_id}
-Iteration: {iteration}
-
-Build:
-├── Status: ✅ SUCCESS
-├── Command: {build_cmd}
-└── Duration: {time}
-
-Database Migration:
-├── Status: ✅ SUCCESS / ⏭️ SKIPPED (no migrations)
-├── Scripts Executed: {count}
-└── Tables Affected: {list}
-
-Application:
-├── Status: ✅ RUNNING
-├── URL: {health_url}
-└── Health: OK
-
-Smoke Test:
-├── Status: ✅ PASSED
-├── Endpoints Tested: {count}
-└── All Returning Expected Status Codes
-
-➡️ Ready for testing phase. Confirm to proceed?
-```
-
-### 3.2 User Confirmation Required
-
-**Wait for user response**:
-
-| User Response | Action |
-|---------------|--------|
-| Confirmed / Yes / Proceed | Execute Phase 3.3 (Finalize) |
-| Rejected / No / Issues found | STOP — Ask user for specific issues |
-| Request details | Provide more information, then re-ask confirmation |
-
-### 3.3 Finalize After Confirmation
-
-**Write final checkpoint**:
-```bash
-node speccrew-workspace/scripts/update-progress.js write-checkpoint \
-  --file speccrew-workspace/iterations/{iteration}/05.deployment/.checkpoints.json \
-  --stage 05_deployment \
-  --checkpoint deployment_complete \
-  --passed true \
-  --description "Deployment verified: build, migration, startup, smoke test all passed"
-```
-
-**Finalize workflow progress**:
-```bash
-node speccrew-workspace/scripts/update-progress.js update-workflow \
-  --file speccrew-workspace/iterations/{iteration}/WORKFLOW-PROGRESS.json \
-  --stage 05_deployment --status confirmed \
-  --output "05.deployment/deployment-report.md"
-```
-
-**Report completion**:
-```
-✅ Deployment Stage Complete
-
-All deployment steps verified:
-- Build: SUCCESS
-- Migration: SUCCESS/SKIPPED
-- Startup: SUCCESS
-- Smoke Test: PASSED
+## AgentFlow Definition
 
-The system is now ready for the testing phase.
-You can proceed with System Test Agent (speccrew-test-manager).
-```
+<!-- @skill: speccrew-system-deployer-orchestration -->
 
 ---
 
@@ -815,6 +366,4 @@ You can proceed with System Test Agent (speccrew-test-manager).
 
 ---
 
-## AgentFlow Definition
 
-<!-- @skill: speccrew-system-deployer-orchestration -->