blueprint-split

Blueprint Split — Convert Flat Blueprint to Nested

A blueprint that holds 300+ entries (or mixes unrelated concerns) is a hotspot for merge conflicts and cognitive overhead. RFC #10 defines a nested split format where one large blueprints/{dir}.yaml is broken into blueprints/{dir}/{group}.yaml files keyed by the second path component.

This skill performs the conversion safely and reversibly.

When to Use

• User types /blueprint-split {dir}
• User says "split this blueprint", "이 블루프린트 쪼개", "분할"
• The session-start advisory recommends /blueprint-split for a specific large blueprint

Usage

/blueprint-split src
/blueprint-split .claude

The argument is the top-level directory name as it appears in the blueprint filename (without the .yaml extension and without the _ prefix that hides dot-directories). Hidden directories like .claude should be passed as .claude, not _claude — the skill normalizes internally.

Instructions

Step 1: Validate Inputs

1. Check the user supplied a directory argument. If not, list the current top-level blueprints (ls .omniscitus/blueprints/*.yaml) and ask which one to split.

2. Verify the target blueprint file exists:

   • blueprints/{normalize(dir)}.yaml (where normalize = leading . becomes _)
   • If not, report the available blueprint files and stop.

3. Verify the target is not already split: check that blueprints/{normalize(dir)}/ directory doesn't exist. If it does, report that the blueprint is already nested and stop. The user can use /blueprint-merge {dir} to undo first.

Step 2: Read the Existing Blueprint

Read the entire blueprints/{normalize(dir)}.yaml file. Parse all entries — paths, status, source, change_log, purpose, etc.

For each entry, compute its bucket by taking the second path component:

• src/lib/auth.ts → bucket = lib
• src/index.ts → bucket = _root (file is at the top of src/)
• .claude/skills/foo.md → bucket = skills
• .claude/CLAUDE.md → bucket = _root