lens-split-feature

Validates split boundaries and moves stories between governance features via scripted operations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve? Splitting an existing feature into a new feature requires careful coordination: validating that no selected story is in-progress, creating a complete new feature shell in the governance repo, and moving story files without corrupting governance metadata. This Skill enforces that sequence so splits stay atomic and auditable. ## Core Features & Use Cases - Split Validation: Runs validate-split against a sprint plan or story files and hard-stops if any selected story is in-progress. - Feature Shell Creation: Creates the new feature directory with feature.yaml, summary.md, a stories/ folder, and a feature-index.yaml entry, with duplicate detection. - Story Migration with Dry-Run: Moves story files between features with dry-run previews, destination conflict checks, and rollback on partial failure. - Use Case: You want to carve MFA stories out of an auth-login feature into a new auth-mfa feature. The Skill validates the boundary, confirms the plan, dry-runs the creation and moves, then executes and reports any stale feature: frontmatter. ## Quick Start Ask the assistant to split stories story-3 and story-4 from the auth-login feature into a new auth-mfa feature, starting with validation and a dry-run before live execution.

Frequently Asked Questions about lens-split-feature

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

FAQPage Schema
How do I split a feature into a new feature in a governance repo?

Run validate-split first to confirm no selected story is in-progress, then dry-run create-split-feature to preview the new feature shell, and finally dry-run move-stories before live execution. Each mutating step requires explicit user confirmation.

How do I move stories between features without losing work?

Use the move-stories subcommand with --dry-run to preview planned moves, then execute live. The script blocks in-progress stories, checks destination conflicts, and rolls back completed moves if any transfer fails.

What happens if a story is in-progress during a split?

The split hard-stops. validate-split and move-stories both normalize story statuses and block any story resolving to in-progress, returning the blocked story IDs with no workaround path.

Does the split feature script prevent duplicate feature IDs?

Yes. create-split-feature reads feature-index.yaml and fails with a duplicate_feature error if the new feature ID is already registered. It also fails if the target feature directory or feature.yaml already exists.

Does move-stories update story frontmatter automatically?

No. After moving, the Skill scans moved story files and reports any whose feature: frontmatter still references the source feature ID, but it never rewrites those files automatically; stale values are surfaced for manual resolution.