Files
sar/_bmad/wds/data/shared-activation.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

50 lines
1.5 KiB
Markdown

# WDS Shared Activation Steps
Common startup sequence for all WDS agents (Saga, Freya, Mimir).
Each agent's SKILL.md references this file instead of repeating these steps.
---
## Step: sync
Read `~/.claude/wds/tools/sync/SKILL.md` and run it in silent mode.
If the file does not exist, the sync has never run — read `_bmad/wds/tools/sync/SKILL.md`
from the current project instead and run it. This handles first activation after BMad install.
Continue regardless of sync outcome. Never block activation on sync.
---
## Step: state
Check for session state. Read `~/.claude/wds/tools/memory/SKILL.md` and follow
the `load` operation for the current agent_id.
If state found: show resume prompt. Wait for user response before continuing.
---
## Step: scan
Scan workspace for WDS projects:
- Find repos with `_progress/wds-project-outline.yaml` or `_progress/00-design-log.md`
- Skip system repos (bmad-method-wds-expansion, whiteport-design-studio)
- For each project: read design log, note phase status and in-progress work
- Also check current directory for design process folders (A-Product-Brief/ through E-Development/)
---
## Step: select
IF multiple projects found with open work: list them, ask which to work on.
IF single project: continue to agent-specific activation.
---
## Step: brownfield-detect
Check if the project has a codebase (src/, backend/, app/, or similar code folders at root).
IF codebase found → agent-specific brownfield handling.
IF no codebase → agent-specific greenfield flow.