Content lifecycle
On this page
This page is generated from docs/source/concepts-content-lifecycle/ — each section below links to its own source.
The content lifecycle
Every content type moves through the same lifecycle, provided by the
cross-cutting content-lifecycle skill package:
BPMN 2.0 source · full-size SVG
| Stage | Skill | What happens |
|---|---|---|
| plan | content-plan | Scope the work, identify artifacts and actors |
| author | content-author | Create structured artifacts from source material |
| validate | content-validate | Check against schema + constraints |
| review | content-review | Human / SME review against criteria |
| test | content-test | Automated QA, build green, proofs/validators pass |
| publish | content-publish | Render and deploy the published form |
| feedback | content-feedback | Capture and route reviewer feedback |
| retire | content-retire | Deprecate or archive an artifact |
The lifecycle stages are the same regardless of content type — what differs is the authoring skills and the artifacts each type produces. For the full list of skills and the roles that drive them, see Skills & roles.
Two things the eight stage names hide, and the diagram does not: author and
validate are not consecutive phases but a loop — every proposed change runs
the HCI validation gate, and the editor sees the findings before anything is
committed — and review happens twice, once per change and once over the
assembled draft. Both expand into their own diagrams on the
publication workflow page.