plan-split

Decompose master implementation plans into sequential sub-plans with blocked_by and blocks metadata.

2|Updated Nov 16, 2024
One-click install
npx skills add https://github.com/onairmarc/dotfiles --skill plan-split-onairmarc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-split
Source: https://github.com/onairmarc/dotfiles/tree/main/.agents/skills/plan-split
Command: npx skills add https://github.com/onairmarc/dotfiles --skill plan-split-onairmarc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose master implementation plans into sequential, self-contained sub-plans written alongside the source plan, with dependency (blocked_by/blocks) headers to guide execution and handoffs.

Core Features & Use Cases

  • Breaks a master plan into ordered sub-plans that can be assigned or executed independently.
  • Ensures cross-sub-plan dependencies are mirrored (blocked_by and blocks) for deterministic sequencing.
  • Produces self-contained sub-plans with clear context and acceptance criteria ready for implementation.

Quick Start

Split a master implementation plan into sequential, self-contained sub-plans alongside the source plan.

Frequently Asked Questions about plan-split

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

FAQPage Schema
How do I split a master implementation plan into sequential sub-plans?

To split a master implementation plan, decompose the source document into ordered, self-contained sub-plan files written alongside the original. Each sub-plan includes context and acceptance criteria for independent execution.

What is plan splitting in project management workflows?

Plan splitting in project management decomposes a master plan into phases, stages, or parallel workstreams. It preserves the original master plan steps while producing self-contained sub-plans for reference and execution.

How do dependencies and handoffs work when splitting a project plan?

Dependencies and handoffs in plan splitting use blocked_by and blocks metadata headers. This mirroring ensures deterministic sequencing across sub-plans so cross-plan dependencies are clearly identified before execution begins.

Can I assign sub-plans to independent teams after decomposing a master plan?

You can assign sub-plans to independent teams because the decomposition produces self-contained files with clear context and acceptance criteria. The structured metadata ensures each team understands its workstream dependencies and handoff requirements.

What's the best way to manage parallel workstreams in an implementation plan?

The best way to manage parallel workstreams is decomposing the master plan into self-contained sub-plans. This approach enforces cross-sub-plan dependencies through blocked_by and blocks metadata for deterministic sequencing.