Julian/sar

Files

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.7 KiB

Raw Permalink Blame History

/handoff — Cross-Agent Handoff

Pass a specific piece of work to another WDS agent. This is NOT a session wrap — it is a targeted transfer of one task or artifact to a different agent.

Usage: /handoff [target-agent] Example: /handoff mimir

- Derive everything from the conversation. Do NOT ask questions. - Do NOT summarize this session. That is a wrap, not a handoff. - Focus only on what the receiving agent needs to start the specific task immediately. - Handoff is written to `progress/[target_agent].md` — the receiving agent picks it up via `/start`. Determine: - `target_agent` — from the argument. If none: infer from context (strategy → saga, design → freya, implementation → mimir). - `from_agent` — your current agent base name. - `project` — current project repo name.

Compose the handoff content — what the receiving agent needs to start immediately:

```
## Task
[Single specific task being handed off. What it is, what state it's in, what remains.]

## Files
[Full absolute paths to every relevant file. The receiving agent should never have to search for them.]

## Next
[Single immediately-actionable next step for the receiving agent.]
```

This is task context, not session history. Always include full absolute file paths — never just filenames. If the receiving agent doesn't need something to do the task, leave it out.

Print EXACTLY this block:

── Handoff to [target_agent] ─────────────────
Task:    [one-line task description]
Next:    [the Next line you composed]
──────────────────────────────────────────────

Then proceed immediately to step 3.

Spawn a sub-agent with this exact prompt — substitute the bracketed values:

---
You are a handoff writer. Your only job is to save a handoff file via the memory tool.

**Step A — Save handoff via memory tool:**
Read `~/.claude/wds/tools/memory/SKILL.md` and follow the `save` operation:
- agent_id: [target_agent]
- data:
```
## Wrapped
[current date and time]

## Context
[task content from step 1]

## Next
[next line from step 1]

## Learned
None

## Spec Sync
None
```

**Step B — Confirm:**
Return ONLY: `done`
---

Wait for the sub-agent to return. Then print EXACTLY this — nothing before, nothing after:
```
/[target_agent] progress/[target_agent].md
```

Session continues.

2.7 KiB Raw Permalink Blame History

/handoff — Cross-Agent Handoff

2.7 KiB

Raw Permalink Blame History