lens-lifecycle

Routes, validates, and advances NextLens feature lifecycle phases using local feature.yaml records.

Updated Apr 7, 2026

Search Tags:#python #yaml #feature planning #sprint planning #lifecycle #workflow routing #phase validation

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve? Managing multi-phase feature planning workflows (preplan, businessplan, techplan, finalizeplan, dev) requires tracking which artifacts exist and which phase comes next. This Skill automates that routing and validation for the NextLens Two-Tree model without depending on lens.core. ## Core Features & Use Cases - Phase Routing: Suggests the next lifecycle phase for a feature based on its track (full or express) and current state in feature.yaml. - Artifact Validation: Checks that required planning documents (prd.md, architecture.md, stories/*.md, etc.) exist before a phase can be marked complete. - Phase Advancement: Updates the local feature record to mark a phase complete, with dry-run and force options for recovery. - Use Case: After finishing tech planning for a feature, run suggest-next to confirm all techplan artifacts exist and get routed to finalizeplan. ## Quick Start Ask the assistant to suggest the next lifecycle phase for feature-id my-feature using the lens-lifecycle script with the project root.

Frequently Asked Questions about lens-lifecycle

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

FAQPage Schema

How do I validate a NextLens lifecycle phase before advancing?▼

Run lifecycle_ops.py with the validate-phase command, passing --project-root, --feature-id, and --phase. It checks that all required artifacts for that phase exist in the feature's docs directory and returns a pass or fail status with missing files listed.

How do I find the next phase for a feature in the Two-Tree model?▼

Use the suggest-next command with the feature ID. The script reads feature.yaml, determines the track (full or express), checks predecessor completion, and returns the recommended next phase or routes completed features to lens-doctor.

What is the difference between full and express tracks?▼

The full track runs preplan, businessplan, techplan, finalizeplan, then dev. The express track skips to expressplan, finalizeplan, then dev, requiring consolidated business-plan, tech-plan, and sprint-plan documents instead of separate artifacts.

Can I advance a phase when required artifacts are missing?▼

Yes, but only with the --force flag on advance-phase, intended for recovery scenarios. Without it, advancement is blocked until all required files and glob patterns for the phase exist in the feature's docs directory.

Does this lifecycle script depend on lens.core?▼

No. The script is a clean-room implementation that never imports or invokes lens.core. It uses only the Python standard library and reads feature state directly from docs/features/<feature-id>/feature.yaml.