Files
sar/.claude/skills/bmad-story-automator/steps-c/step-03c-execute-complete.md
julian 17c08e6392 chore: initial monorepo scaffold + WDS Phase 1+2 artifacts
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24)
- apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004)
- apps/web: React 19 + Vite 8 (ESM)
- libs/shared/api-interface: Zod contract base
- Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit
- WDS artifacts:
  - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs)
  - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact)
- Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md
- AGENTS.md + README.md como entrada para devs/agentes

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-27 14:34:20 +00:00

2.2 KiB

name, description, nextStep, scriptsDir, outputFile, executionPatterns, retryStrategy, triggers
name description nextStep scriptsDir outputFile executionPatterns retryStrategy triggers
step-03c-execute-complete Post-loop completion summary, parallelism notes, and transition to wrapup ./step-04-wrapup.md ../scripts/story-automator {output_folder}/story-automator/orchestration-{epic_id}-{timestamp}.md ../data/execution-patterns.md ../data/retry-fallback-strategy.md ../data/escalation-triggers.md

Step 3c: Execution Complete

Goal: Summarize results after all stories finish, persist final status, and transition to wrapup. Interaction mode: Deterministic auto-proceed.


All Complete

Display:

**All {count} stories completed!**

If `{count} <= 10`:
| Story | Status |
|-------|--------|
{summary_table}

If `{count} > 10`:
- Completed: {completed_count}
- Warnings: {warning_count}
- Escalations: {escalation_count}
- See state log for full per-story table.

Proceeding to wrap-up...
"{scriptsDir}" orchestrator-helper state-update "{outputFile}" \
  --set status=EXECUTION_COMPLETE --set lastUpdated="$(date -u +%Y-%m-%dT%H:%M:%SZ)"
echo "- **[$(date -u +%Y-%m-%dT%H:%M:%SZ)]** All stories complete — execution finished" >> "{outputFile}"

Parallelism & Escalation

Parallelism: When overrides.maxParallel > 1, batch independent stories into concurrent groups:

  1. Check story dependency graph — only stories with no shared file dependencies can run in parallel
  2. Spawn up to maxParallel tmux sessions simultaneously (each runs steps A→F independently)
  3. Wait for all sessions in the batch to complete before starting the next batch
  4. Epic completion check (H) runs only after all batches finish

See {executionPatterns} for forbidden patterns and session isolation rules.

Escalation: See {triggers} for trigger definitions and {retryStrategy} for retry/fallback patterns. Escalation only after exhausting all retry attempts.

Auto-Proceed to Wrap-up

Display: "Execution loop complete. Proceeding to wrap-up..."

"{scriptsDir}" orchestrator-helper state-update "{outputFile}" \
  --set currentStep=step-04-wrapup \
  --set lastUpdated="$(date -u +%Y-%m-%dT%H:%M:%SZ)"

Then

→ Immediately load and execute {nextStep}