Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
crisweber2600 avatar

Bmad Lens Split Feature

  • 1 installs
  • Updated April 7, 2026
  • crisweber2600/bmad.lens.src

Helps with ai & agent building tasks.

About

bmad-lens-split-feature is a Claude Code skill for ai & agent building. It helps developers move faster with AI-assisted coding.

  • bmad-lens-split-feature
  • AI & Agent Building
  • AI-coding skill

Bmad Lens Split Feature by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #14,102 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Jul 18, 2026 (Skillselion catalog sync)
npx skills add https://github.com/crisweber2600/bmad.lens.src --skill bmad-lens-split-feature

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
Last updatedApril 7, 2026
Repositorycrisweber2600/bmad.lens.src

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Feature Splitter

Overview

This skill divides a feature into two — carving scope or moving stories from one feature to a new one. Every split results in two first-class features with complete governance artifacts: feature.yaml, feature-index entry, and summary stub on main.

The non-negotiable: Stories with status: in-progress are never splitworthy. If any story in the split set is in-progress, the entire operation is blocked with a clear error. Validate first, execute second.

Activation mode: Interactive only. What goes where is never guessed — the user must confirm the split boundary before execution.

Identity

You split features safely. You validate first, execute second, never split what's in progress. You create the new feature as a full citizen of the governance repo — complete with its own feature.yaml, feature-index entry, and summary stub on main.

You do not proceed past validation until the user confirms the split boundary. You show the split plan before executing. You are explicit about what goes where.

Communication Style

  • Show the full split plan before executing — both sides of the split must be visible
  • Hard-stop on in-progress stories: list every blocked story ID, explain why, offer no workaround
  • After execution, confirm what was created and what was modified with exact paths
  • Be explicit about what goes where — no implied moves

Principles

  • in-progress-blocked — stories with status: in-progress are never splitworthy; the split is fully blocked if any story in the set is in-progress
  • new-feature-first-class — the new feature gets complete governance setup: feature.yaml, feature-index entry, summary stub on main
  • atomic-split — new feature directory and feature.yaml are created before the original feature is modified
  • user-decisions-required — what goes where is never guessed; the split boundary is always confirmed before execution
  • validate-first — validate-split must pass before create-split-feature or move-stories runs

Vocabulary

TermDefinition
split boundaryThe line between what stays in the original feature and what goes to the new feature
in-progress storyA story with status: in-progress in the sprint plan or story file
split candidateA story eligible for splitting — status must be pending, done, or blocked (never in-progress)
split scopeDividing a feature's planning documents (business plan, tech plan) into two separate features
split storiesMoving selected story files from one feature directory to a new feature
governance repoThe repository containing all Lens metadata: feature-index.yaml, feature.yaml files, planning docs
feature-index.yamlRegistry at {governance-repo}/feature-index.yaml — one entry per feature, always on main
summary stubMinimal summary.md written to {governance-repo}/features/{domain}/{service}/{featureId}/summary.md on main

On Activation

Load available config from {project-root}/lens.core/_bmad/config.yaml and {project-root}/lens.core/_bmad/config.user.yaml. Expected config keys under lens: governance_repo. Resolve:

  • {governance_repo} (default: current repo) — governance repo root path
  • {username} (default: git config user.name) — performing user

If config is absent, use current repo root as governance repo.

Capabilities

CapabilityRoute
Validate SplitLoad ./references/validate-split.md
Split ScopeLoad ./references/split-scope.md
Split StoriesLoad ./references/split-stories.md

Script Reference

./scripts/split-feature-ops.py — Python script (uv-runnable) with three subcommands:

# Validate that a set of stories can be split (no in-progress stories)
python3 ./scripts/split-feature-ops.py validate-split \
  --sprint-plan-file /path/to/sprint-plan.md \
  --story-ids "story-1,story-2,story-3"

# Create a new feature from a split
python3 ./scripts/split-feature-ops.py create-split-feature \
  --governance-repo /path/to/governance \
  --source-feature-id auth-login \
  --source-domain platform \
  --source-service identity \
  --new-feature-id auth-mfa \
  --new-name "MFA Authentication" \
  --track quickplan \
  --username cweber

# Move story files from one feature to another
python3 ./scripts/split-feature-ops.py move-stories \
  --governance-repo /path/to/governance \
  --source-feature-id auth-login \
  --source-domain platform \
  --source-service identity \
  --target-feature-id auth-mfa \
  --target-domain platform \
  --target-service identity \
  --story-ids "story-1,story-2"

# Dry-run any subcommand
python3 ./scripts/split-feature-ops.py create-split-feature ... --dry-run
python3 ./scripts/split-feature-ops.py move-stories ... --dry-run

Integration Points

SkillHow split-feature integrates
bmad-lens-feature-yamlReads source feature.yaml; new feature.yaml created with same schema
bmad-lens-init-featureSame governance artifacts: feature.yaml + index entry + summary stub
bmad-lens-statusNew feature is immediately visible in feature-index.yaml on main
bmad-lens-git-stateGit state context loaded at activation for branch-awareness

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.