What problem does it solve? When splitting a large initiative into child tasks across one or more repositories, teams need a consistent way to bootstrap each child's execution packet without copying the entire parent initiative or losing traceability. This Skill creates a clean, minimal child packet in the selected child row's Packet Root so planning can start from a well-defined baseline. ## Core Features & Use Cases - Packet Bootstrapping: Creates INDEX.md, BRIEF.md, PLAN.md, AMENDMENTS.md, and ARTIFACT_CANDIDATES.md under .plans/<task-slug>/ with required bootstrap semantics such as Status: not_authored and Packet phase: hydrated_for_planning. - Cross-Repo Context Handling: Writes child-packet references from the child repo's perspective, using relative paths or repo-qualified references for the parent initiative instead of pasting raw cross-repo locators. - Parent Graph Updates: Sets the hydrated child row in TASK_GRAPH.md to active without mutating parent initiative status. - Use Case: After an initiative split review is marked ready, hydrate the chosen child row into its owner repo so the child team gets a frozen subset of parent context and can begin authoring its own plan. ## Quick Start Hydrate the ready child row from TASK_GRAPH.md into its Packet Root so the child task packet is bootstrapped for planning.
