lens-finalizeplan

Run FinalizePlan with the feature ID after TechPlan or ExpressPlan reaches a complete state. It validates the predecessor gate, runs the adversarial review, publishes artifacts, creates the planning PR, and generates the downstream dev bundle.

The bundle includes epics.md, stories.md, implementation-readiness.md, sprint-status.yaml, and individual story files. These are produced by delegating to BMAD wrapper skills in a fixed order: epics-and-stories, implementation-readiness, sprint-planning, then create-story.

Yes, but only for a phase-complete resume where review-ready validation proves the predecessor artifacts are complete. Otherwise it stops and reports that TechPlan or ExpressPlan completion is required first.

A fail verdict stops the flow immediately. No publishing, commits, PRs, or feature.yaml phase updates occur, and the lifecycle state remains unchanged until findings are resolved.

No. All governance writes route through the publish-to-governance CLI, lens-git-orchestration, or lens-feature-yaml. Direct authoring or patching of files in the governance repo is explicitly forbidden.

It should not when the track-specific input-ready contract passes. For express-track features, business-plan.md, tech-plan.md, and sprint-plan.md satisfy the input gate; generic BMAD document names are not blockers.