lens-doctor

Diagnoses Lens topology health and routes findings to remediation workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Lens knowledge topologies accumulate defects like duplicate stable IDs, broken parent links, and stale metadata that silently block projection rebuilds. This Skill runs read-only health checks that separate blocking defects from advisory warnings and tell you exactly which workflow can fix each finding. ## Core Features & Use Cases - Blocking Defect Detection: Identifies duplicate published stable IDs, missing required metadata, invalid ID prefixes, broken belongs_to references, parent cycles, and broken local links. - Advisory Triage: Flags draft parent gaps, unpromoted completed knowledge, Salmon signals, and stale timestamps that do not block projections. - Workflow Routing: Produces a compact doctor report with JSON output and routes each finding to the owning workflow such as lens-topology-design, lens-ledger-promotion, or lens-salmon-impact. - Use Case: Before rebuilding published projections, run a doctor check to confirm no blocking defects exist, then follow the routing guidance to resolve any findings. ## Quick Start Ask the assistant to run lens doctor against the project to check topology health and report any blocking or advisory findings.

Frequently Asked Questions about lens-doctor

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

FAQPage Schema
How do I check Lens topology health before rebuilding projections?

Run the lens doctor command, which executes the lens_projection.py script in doctor mode against your work intake path, feature archive path, and landscape root. It reports blocking findings, advisory findings, and whether a projection rebuild is ready.

What blocking defects does a topology health check detect?

Blocking findings include duplicate published stable IDs, missing required metadata, invalid stable ID prefixes, broken belongs_to references, parent type mismatches, parent cycles, broken local links, and completed features with no resolvable ledger target.

Does lens doctor modify my archives or ledgers?

No, lens doctor is strictly read-only. It never edits archives, ledgers, projections, or config files; it only describes fixes with exact source paths and routes you to the owning workflow.

What is the difference between blocking and advisory findings?

Blocking findings prevent published projection rebuilds and must be fixed first. Advisory findings like draft parent gaps, unpromoted knowledge, Salmon signals, and stale timestamps do not make projections unsafe but indicate cleanup opportunities.

What should I do after a clean lens doctor report?

After a clean doctor status, run lens-projection-rebuild followed by lens-reporting-snapshot. If findings exist, route to lens-topology-design for metadata blockers, lens-ledger-promotion for unpromoted knowledge, or lens-salmon-impact for Salmon signals.