How Magpie fits together

Choose your tools without rewriting the workflow

Skills ask for a capability rather than a named vendor. Tools implement each capability for a backend, so your project can change its tracker, mail, model or agent while keeping the workflow. Neutrality holds on six independent axes; a choice on one never constrains the others.

10 of 12 capability contracts (83%) have at least 2 backends or are neutral by construction. 78 of 78 skills are vendor-neutral, and 29 of 29 low-level tools work with any agent.

Keep your project’s conventions

Most tool choices are the same for every project under one governing organization: every ASF project allocates CVEs the same way, reads the same mail archive and gates on PMC membership. An organization profile holds those shared defaults once: its governance vocabulary, the backend each capability uses, and its identity. A project names its organization and inherits the rest; its own configuration still wins, then the organization, then the framework default. The same skill runs unchanged for an ASF project and an independent one; the organization carries the difference.

Any foundation, company or collective can add its own: contribute it to the framework so its projects and others reuse it, keep it in the organization’s own repository, or keep one locally in a project’s overrides.

Explore the reference

The capability and tool definitions below come from the framework. Implementation status and supported vendors are available in the tools directory.