What problem does it solve? When discovery shows work is too large for a single task, teams need a structured parent initiative packet before child tasks can be split. This Skill creates that packet once, with a canonical file tree, so later phases update existing files instead of inventing ad hoc structure. ## Core Features & Use Cases - Canonical Packet Creation: Creates .initiatives/<initiative-slug>/ with every required top-level file from the initiative packet contract. - Seeded Shared Context: Seeds INDEX.md, BRIEF.md, DECISIONS.md, INVARIANTS.md, REPO_MAP.md, CONTRACTS.md, and OPEN_QUESTIONS.md with current discovery facts, plus placeholder stubs for UBIQUITOUS_LANGUAGE.md, TASK_GRAPH.md, and SYNC_LOG.md. - Status Lifecycle: Bootstraps with Status: discovery and exits with Status: framed, leaving unknowns explicit rather than inventing certainty. - Use Case: After discovery reveals a multi-part feature, run this Skill to frame the initiative packet so a fresh agent can immediately see the problem, invariants, contracts, and open questions before child task packets are split. ## Quick Start Use the frame-initiative skill to create a parent initiative packet for the newly discovered multi-part work under .initiatives/.
