Extensions
Specialize a workspace with work types, workflows, personas, tools and screens.
An extension specializes Outcome for one kind of work, such as engineering, architecture, testing or publishing. It adds request types, work types and their workflows, personas, knowledge scopes, tools and screens.
Extensions are data only: they run no code on the Outcome server. Each one ships as its own GitHub repository (or its zip) and is installed from a catalog. Screens are built from the platform's block library; when an extension needs custom UI, its components run only in a sandboxed frame in the client.
Built-in extensions
| Extension | For |
|---|---|
| Engineering | Planning, building and shipping software |
| Architecture | Designs, ADRs and approvals |
| Testing | Test plans and verification |
| Designer | Building and validating new extensions |
| Book | Long-form writing and editing |
| Production and Post | Media production pipelines |
Build your own
The extension designer is itself an extension. Its work items produce an extension draft, and its checks run
out extension validate and out extension test.