cpo-wiki
Writes and updates evergreen wiki pages: stable, current-state explanations of how the product works, readable by anyone. Brainstorms, plans, and release notes stay in their own homes until the behavior is settled.
When to use it
Section titled “When to use it”- stable product behavior deserves an explainer
- a change on a card’s branch makes an existing page out of date
What it needs
Section titled “What it needs”- a configured repo with a wiki path in config
- the wiki’s own README, which owns the page contract — this skill follows it rather than forking its rules
What you get
Section titled “What you get”- an evergreen page, or an updated one, in the
cpo-writeregister with the project’s own vocabulary
Where it sits
Section titled “Where it sits”Pages ride the card’s own PR: a page made wrong by a change is fixed on
that change’s branch, before human review, by the agent that made the
change. cpo-ship checks that promised pages appear in the merged diff.
The wiki also carries the shared vocabulary — a glossary page from
CONTEXT.md and a decisions page from the ADRs — so the technical team
and the wiki use the same words.
Say this
Section titled “Say this”cpo-wikiadd this to the wikiwrite a wiki page about signals