with one click
memory
// Session state backend for WDS. Called by wrap, start, and handoff tools — never directly by users. Writes to progress/ in the project repo.
// Session state backend for WDS. Called by wrap, start, and handoff tools — never directly by users. Writes to progress/ in the project repo.
Syncs WDS skills from the current project (_bmad/wds/) to ~/.claude/commands/ so they work in any project. Called automatically on every agent activation.
Implementation agent. Owns the tech audit, the PRD, and the build. Reads Freya's Work Orders and turns them into working code — one verified task at a time.
Strategic UX designer and design thinking partner for WDS. Use when the user asks to talk to Freya or requests the WDS designer.
Strategic business analyst and product discovery partner for WDS. Use when the user asks to talk to Saga or requests the WDS analyst.
Create UX scenario outlines from Trigger Map through structured micro-steps
Establish project context - foundation for all design work
| name | memory |
| version | 1.0.0 |
| description | Session state backend for WDS. Called by wrap, start, and handoff tools — never directly by users. Writes to progress/ in the project repo. |
| agents | ["saga","freya","mimir"] |
Handles all persistent state for WDS sessions. Two operations: save and load.
State lives in progress/ at the project root. This folder is project-scoped — not global, not per-machine.
Called by: wrap (step 3), handoff (step 3)
Input:
agent_id — the agent whose state is being saved (saga, freya, mimir)data — the compiled state block (Wrapped, Context, Plan, Next, Learned, Spec Sync fields)Steps:
progress/ exists at the project root. Create it if not.progress/[agent_id].md with the data block exactly as provided.saved progress/[agent_id].mdCalled by: start (step 2)
Input:
agent_id — the agent whose state is being loadedSteps:
progress/[agent_id].md exists.progress/ should be in .gitignore. It is machine-local session context, not project content.