The pack is the whole delegate workflow packed into a single tree that travels intact. Its entrypoint is skills/delegate/SKILL.md, and everything that entrypoint references lives beside it: the transitively-called skills under skills/, three role prompts under roles/, two shared workflow documents under docs/, and a manifest.json that records the dependency graph in machine-readable form. Fifteen skills in total, six original and nine MIT-licensed from the Superpowers set, with ship-gate deliberately left out. Nothing in the tree points outside the tree.

open ⤢
One tree, four shelves, a manifest. The entrypoint, the skills, the roles and the docs all resolve inside the checkout, so nothing it needs is somewhere else.

The frame is bill of materials, not framework. The pack executes nothing on its own; it is a tree of instructions plus a manifest plus a small installer. The discipline a good workflow depends on tends to grow tangled inside one particular tool's config and one particular machine's skill directory, portable in principle and trapped in practice. Packing the entire dependency graph into one checkout is what lets the workflow move to a different agent without falling apart, because half of what it needs is no longer somewhere else.