lens-reporting-snapshot

Generates read-only stakeholder status snapshots in Markdown and JSON from Lens governance artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Stakeholders need a consolidated, time-bound view of Lens project health without manually reading feature archives, ledgers, audit reports, and topology decisions scattered across the repository. ## Core Features & Use Cases - Read-Only Snapshot Generation: Produces Markdown and JSON snapshot artifacts from feature archives, living ledgers, map audits, promotion reports, Salmon impact reports, and topology decisions without mutating any source files. - Blocking vs Advisory Separation: Carries forward blocking findings from preflight, audit, lifecycle, constitution, and Salmon reports while keeping advisory cleanup items distinct. - UI-Ready JSON Contract: Emits a schema-validated JSON snapshot with summary cards, facets, artifact index, freshness, and refresh metadata for future Lens UI ingestion. - Use Case: A project lead asks for a stakeholder status report before a steering meeting; the skill reads the latest governance artifacts and writes snapshot-{date}.md and snapshot-{date}.json with an overall GREEN/YELLOW/RED status and recommended next actions. ## Quick Start Ask the assistant to create a Lens reporting snapshot for the current project and review the generated Markdown and JSON files under the reporting output path.

Frequently Asked Questions about lens-reporting-snapshot

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

FAQPage Schema
How do I create a stakeholder status report from Lens artifacts?

Request a Lens reporting snapshot and the skill reads feature archives, ledgers, and recent audit reports, then writes snapshot-{date}.md and snapshot-{date}.json under the configured reporting output path. It defaults to an executive audience with overall health, risks, and next actions.

What inputs does the Lens reporting snapshot use?

It reads feature archives, living ledgers, and recent preflight, lens-doctor, map-audit, governance-map, ledger-promotion, salmon-impact, and topology-decision reports. Reports older than the freshness threshold (default 24 hours) are flagged as advisory.

Does the snapshot workflow modify source governance files?

No, the workflow is strictly read-only toward feature archives, ledgers, topology decisions, and prior reports. Its only writes are the snapshot Markdown and JSON artifacts under the reporting output path.

Can the snapshot JSON be consumed by a UI application?

Yes, the JSON follows a published schema with summary cards, facets, artifact index, search fields, and refresh metadata designed for UI ingestion. Access enforcement remains the responsibility of the hosting application.

How are blocking and advisory findings handled in snapshots?

Blocking findings from the latest preflight, audit, lifecycle, constitution, or Salmon reports are carried forward as blocking snapshot risks, while advisory items stay separate. The overall status is reported as GREEN, YELLOW, or RED.