lens-work-setup

Registers the LENS Workbench module into BMAD configuration and help systems.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-work-setup-crisweber2600
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lens-work-setup
Source: https://github.com/crisweber2600/Lens.Core.Src/tree/main/_bmad/lens-work/lens-work-setup
Command: npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-work-setup-crisweber2600

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and assets (resource) components.

What problem does it solve? Installing or upgrading a BMAD module requires manually editing the host manifest.yaml and help CSV, which risks stale leftover entries and inconsistent registrations. This Skill automates the registration of the LENS Workbench module using an anti-zombie merge pattern that removes old entries before writing current ones. ## Core Features & Use Cases - Config Merge: Merges the lens module entry from module.yaml into the host BMAD manifest.yaml, removing any pre-existing lens section first. - Help CSV Merge: Registers lens capabilities in the host bmad-help.csv by replacing all existing Lens rows with current entries. - Legacy Cleanup: Removes deprecated flat skill files and legacy data/ directories left over from older module versions, with a dry-run option. - Use Case: After installing or updating the LENS Workbench module, run this Skill to register it in the host configuration, update the help system, verify the installation, and clean up legacy artifacts. ## Quick Start Run the lens-work-setup skill to register the lens module into my BMAD configuration and help system.

Frequently Asked Questions about lens-work-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I register a BMAD module after installation?

Run the merge-config.py script with uv, passing the module's module.yaml and the host manifest.yaml paths. The script removes any existing module entry, then writes the current configuration values into the target manifest.

How to merge module help entries into a CSV help system?

Use merge-help-csv.py with the module's help CSV and the target bmad-help.csv. It derives the module name from the first data row, deletes all existing rows for that module, and appends the current entries.

What is the anti-zombie pattern in config merging?

The anti-zombie pattern removes all existing entries for a module before writing new ones. This prevents stale or duplicated configuration from surviving upgrades, ensuring the target file reflects only the current module version.

Does this setup require any tools installed beforehand?

Yes, uv must be installed because the scripts use PEP 723 inline metadata and are executed via uv run --script. The target BMAD _config directory with manifest.yaml must also exist before running the merge.

How do I clean up legacy files from an older module version?

Run cleanup-legacy.py with the --module-dir argument pointing to the module directory. It removes deprecated flat skill files and empty legacy data directories, and supports --dry-run to preview changes first.