tools/memory and tools/sync SKILL.md names fail BMAD installer SKILL-05 (skipped from manifest)

[thecontstruct]

Summary

During bmad-method install (BMAD core v6.7.1), manifest generation skips two internal WDS tool skills because frontmatter name does not match the parent directory name. The WDS module otherwise installs successfully (v0.4.2).

Error: SKILL.md name "wds-memory" does not match directory name "memory" — skipping
Error: SKILL.md name "wds-sync" does not match directory name "sync" — skipping

Environment

• BMAD core: v6.7.1 (bmad-method installer)
• WDS module: v0.4.2 (02dd2ff)
• Repo: https://github.com/bmad-code-org/bmad-method-wds-expansion
• Install target: _bmad/wds/ (e.g. axonify-bmad)

Root cause

BMAD installer enforces SKILL-05: name in SKILL.md frontmatter must exactly match the skill directory basename.

Source path	Directory	name in frontmatter	Installer result
src/tools/memory/SKILL.md	memory	wds-memory	skipped
src/tools/sync/SKILL.md	sync	wds-sync	skipped

All workflow skills follow the convention correctly (e.g. src/workflows/wds-4-ux-design/ → name: wds-4-ux-design) and install to .claude/skills/.

Enforcement: bmad-method → tools/installer/core/manifest-generator.js (parseSkillMd).

Reproducible with BMAD validator:

node tools/validate-skills.js --json src/tools/memory   # SKILL-05
node tools/validate-skills.js --json src/tools/sync     # SKILL-05

Impact

1. Not registered in BMAD skill manifest / help catalog generation for these two skills.
2. Not copied to .claude/skills/ by the BMAD installer (unlike the 13 wds-* workflow + agent skills).
3. WDS runtime still partially works via file-path fallbacks:
   • shared-activation.md falls back to _bmad/wds/tools/sync/SKILL.md on first activation.
   • wds-sync copies tools/memory/SKILL.md → ~/.claude/wds/tools/memory/SKILL.md by path, not skill id.
4. On a fresh machine with no prior wds-sync run, ~/.claude/wds/ may not exist until an agent activates and runs sync — session memory (wrap, start, handoff) depends on that copy.

Suggested fix

Preferred: Rename source directories to match frontmatter (consistent with workflows):

• src/tools/memory/ → src/tools/wds-memory/
• src/tools/sync/ → src/tools/wds-sync/

Then update path references:

• src/tools/sync/SKILL.md copy table ({WDS_SRC}/tools/memory/...)
• src/data/shared-activation.md fallback (_bmad/wds/tools/sync/SKILL.md → .../wds-sync/...)
• Any other references to tools/memory or tools/sync under src/

Optional: Keep global sync destination as ~/.claude/wds/tools/memory/ (short path) even if source dir is wds-memory — the sync skill already maps source → dest explicitly.

Additional finding (separate or same PR)

src/agents/wds-agent-mimir-builder/SKILL.md activation step references _wds/tools/memory/SKILL.md — stale path after BMAD standardization to _bmad/wds/. Saga/Freya use shared-activation.md with correct _bmad/wds paths; Mimir is the only agent with _wds/.

Read `_wds/tools/memory/SKILL.md` ...

Should be _bmad/wds/tools/... (or updated path if directories are renamed).

Related

• BMAD registry: bmad-modules.yaml → bmad-method-wds-expansion / npmPackage: bmad-wds
• Open issue WDS installer does not create bmad-wds-* skill bindings for Claude Code #14 (different topic: bmad-wds-* vs wds-* naming in help/installer) — may overlap installer expectations but distinct from this SKILL-05 skip.

Acceptance criteria

• bmad-method install with WDS produces no SKILL name/directory mismatch errors for memory/sync tools
• Both tools appear in generated skill manifest (if they should be user/agent discoverable)
• First agent activation + session memory (wrap/start/handoff) work on a clean machine after install only
• Mimir activation uses correct _bmad/wds/... path

[coderabbitai]

🔗 Related PRs

#3 - feat: convert agents to native skill format [merged]
#4 - feat: convert 0-alignment-signoff workflow to native skill format [merged]
#5 - feat: convert 0-project-setup workflow to native skill format [merged]
#32 - fix(skills): align SKILL.md name with directory name for mimir + memory [merged]
#33 - feat(agents): add Mimir to WDS agent roster [closed]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!