split-plan

Split Plan

Transform a master plan into 8 phase-specific implementation plans organized by feature tracks with complexity scoring.

Purpose

Analyze a master plan file and generate 8 separate plan files, one for each phase of clean architecture (Foundational, Models, Services, Data, Rules, State Management, UI, Tests).

Overview

Analyze a master plan file and generate 8 separate plan files, one for each phase of clean architecture:

1. Foundational - Base abstractions, utilities, infrastructure
2. Models - Data entities, DTOs, value objects
3. Services - External APIs, service integrations
4. Data - Repositories, DAOs, local storage
5. Rules - Business logic, use cases, validation
6. State Management - ViewModels, presenters, state handlers
7. UI - Screens, components, widgets
8. Tests - Unit tests, integration tests, test utilities

Inputs

• Master Plan: ${master-plan-path} - The comprehensive plan to analyze
• Base Name: ${base-name} - Prefix for all generated files

Outputs

Eight phase plan files in tasks/${base-name}/plans/:

• ${base-name}-01-foundational.md
• ${base-name}-02-models.md
• ${base-name}-03-services.md
• ${base-name}-04-data.md
• ${base-name}-05-rules.md
• ${base-name}-06-state-management.md
• ${base-name}-07-ui.md
• ${base-name}-08-tests.md

Workflow

1. Analyze Master Plan

Read the master plan from ${master-plan-path} and:

Extract tasks: Identify all implementation tasks from the plan

• Look for numbered lists, bullet points, sections
• Extract task titles and descriptions
• Note dependencies and relationships

Identify feature tracks: Group related tasks by feature/module

• Use lowercase-with-hyphens naming (e.g., "authentication", "user-profile")
• Prefer broader groupings over granular ones
• Ensure tracks can span multiple phases
• Common tracks: authentication, products, cart, notifications, settings

Classify tasks by phase: Determine which phase each task belongs to