Skip to main content

01 · Introduction

Prometheus Skill Pack supplies reusable skills, local KBD workflows, team definitions, hook delivery and optional learning/execution services. A workflow records its plan, task ownership and evidence so another session can resume deliberate work.

What is shared​

Skills and local workflow records can be used by supported harnesses. Installed discovery, hook support, model controls and permissions remain harness-specific. A generated definition is not proof of native activation. Team memory is delivered by owner and scope; Codex parent context receives a metadata digest so a fork does not inherit another role's private lesson text.

The full pack includes shell/Python helpers and optional native services. Mini supplies a Node-only subset for Windows, macOS and Linux. Companion separately owns connected control and synchronization. All three boundaries are explicit: the packs remain usable without Companion.

Work as a loop​

A useful loop has a trigger, a termination condition and an evidence source. It can plan work, assign ownership, produce an implementation and inspect the result. Learning can improve later context when publication and retrieval succeed; a loop does not automatically improve simply because it repeats.

Local KBD records workflow authority. Team task/handoff records describe responsibilities but do not grant permissions to another repository. Prometheus Exec adds a separate bounded operation and signed-receipt boundary when execution evidence is required. Knowledge/memory publication remains its own protocol.

Choose your entry point​

Component versions and support follow their source manifests and release evidence. Reading this guide, building a binary or registering a service does not certify an installed machine.