lens-topology-design

Creates service, domain, and program topology decision reports for Lens projects.

Updated Apr 7, 2026

Search Tags:#domain modeling #lens #service architecture #topology design #decision report #ledger scaffolding

Ready to run

npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-topology-design-crisweber2600

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lens-topology-design
Source: https://github.com/crisweber2600/Lens.Core.Src/tree/main/_bmad/lens-work/skills/lens-topology-design
Command: npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-topology-design-crisweber2600

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Structuring programs, domains, and services in a Lens/BMAD project requires durable decisions about hierarchy, stable IDs, and ledger placement, and doing this ad hoc leads to conflicting folder layouts and lost provenance. ## Core Features & Use Cases - Topology Decision Reports: Produces structured reports with PROPOSED, APPROVED, APPLIED, or BLOCKED status, stable ID tables, and machine-readable JSON summaries. - Ledger Scaffolding: Creates or updates living ledger scaffolds under the landscape root only with explicit approval, using shared Lens templates. - Interactive and Headless Modes: Asks follow-up questions interactively, or writes report-only output with explicit assumptions in headless runs. - Use Case: When reorganizing a monorepo into domains and services, run a topology design pass to get a proposed hierarchy, stable ID assignments, and a migration plan before touching any ledger files. ## Quick Start Ask the assistant to design the service topology for the current Lens project and write a topology decision report.

Frequently Asked Questions about lens-topology-design

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

FAQPage Schema

How do I design a service topology for a Lens project?▼

Invoke the topology design workflow with your project context, and it reads existing ledgers, feature archives, and prior decision reports to produce a proposed hierarchy. The output is a topology decision report with stable IDs, parent references, and a migration plan.

What is a topology decision report in Lens?▼

A topology decision report documents scope, sources, assumptions, current and proposed topology, a stable ID table, blocking inconsistencies, and a scaffold plan. It carries a status of PROPOSED, APPROVED, APPLIED, or BLOCKED plus a machine-readable JSON summary block.

Does topology design modify ledger files automatically?▼

No, ledger scaffolds are only created or updated when the user explicitly approves in interactive mode or passes an explicit apply/scaffold argument in headless mode. Otherwise the workflow writes a report only and never edits source documents.

What happens when a folder path conflicts with a parent reference?▼

The workflow surfaces the conflict instead of collapsing boundaries to fit the folder layout. It explains which authored evidence supports each side and records the inconsistency as blocking or advisory in the decision report.

Can topology design run headless without user interaction?▼

Yes, headless mode writes a decision report from available context and marks unresolved choices explicitly instead of asking questions. It never modifies ledger files in headless runs unless an explicit apply argument is present.