lens-ledger-promotion

Promotes completed feature knowledge into living service, domain, or program ledgers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed feature work often leaves durable decisions and knowledge trapped in archived folders, while living ledgers that teams rely on for current operational truth become stale. This Skill moves durable knowledge from completed, published feature archives into the correct ledgers without erasing the permanent feature history. ## Core Features & Use Cases - Promotion Planning and Apply: Builds a promotion plan separating direct ledger updates, new ledger entries, deferred items, and blocked items, with a dry-run default in headless mode unless --apply is passed. - Provenance Preservation: Adds source_feature references and stable IDs to every promoted entry so ledger content stays traceable to its feature archive. - Blocking and Advisory Classification: Flags missing stable IDs, conflicting parent references, duplicate identities, and blocked Lens preflight status before any write occurs. - Use Case: After closing out a feature in docs/features, run a promotion review to move its durable decisions into the relevant service ledger and receive a report with an APPLIED, PLANNED, PARTIAL, or BLOCKED verdict. ## Quick Start Ask the assistant to run lens ledger promotion for the completed feature folder and produce a promotion plan and report.

Frequently Asked Questions about lens-ledger-promotion

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

FAQPage Schema
How do I promote a completed feature into a living ledger?

Run the promotion workflow against the feature folder in your work intake or archive path. The skill reads the archive and target ledger, builds a promotion plan, and applies ledger edits only after user approval or an explicit --apply instruction.

What qualifies a feature as a promotion candidate?

Candidates typically have status completed or done, an accepted closeout, and publication_state published. Drafts, in-progress work, retired work, and already-promoted records are skipped unless you explicitly request a re-promotion review.

Does ledger promotion delete or rewrite the feature archive?

No. The feature archive remains the immutable delivery record. Promotion copies or synthesizes durable knowledge into ledgers with source_feature references, and archives are only touched to add a user-approved promotion marker.

What happens in headless mode without an apply flag?

Headless runs default to dry-run behavior, producing only a promotion plan and report. Source ledger files are not edited unless the user explicitly passes an apply instruction such as --apply.

Why is a promotion blocked even though the feature is complete?

Blocking findings include missing stable IDs, no resolvable ledger target, conflicting parent references, duplicate entity identity, contradictions with newer ledger entries, or blocked Lens preflight status. The report lists these separately from advisory findings.