What problem does it solve? Finalizing a feature in a Lens governance workflow requires checking phase state, verifying an approved retrospective, updating feature.yaml and feature-index.yaml, writing a summary, and cleaning up control-repo branches. Doing this manually risks inconsistent governance state and orphaned branches. ## Core Features & Use Cases - Precondition validation: The check-preconditions command verifies the feature phase is completable, retrospective.md exists with status approved, and surfaces advisory warnings for missing documentation or orphaned control-repo branches. - Atomic finalize with confirmation gate: The finalize command updates feature.yaml to phase complete, marks feature-index.yaml as archived, writes summary.md, and supports dry-run previews plus an explicit --confirm requirement before any irreversible write. - Control-repo branch orchestration: For 3-branch topologies, finalize validates branch ancestry, merges {featureId}-dev into main via a GitHub CLI pull request, and deletes the plan, feature, and dev branches; flat topologies sync the default branch directly. - Use Case: After finishing development and running a retrospective, ask the assistant to complete the feature. It checks preconditions, shows a dry-run plan, and on confirmation archives the feature and merges the dev branch to main. ## Quick Start Ask the assistant to complete the feature with ID my-feature after confirming the retrospective is approved, and review the dry-run plan before confirming the archive.
