Create and review
Skeleton first, details after review; for new RFCs list open questions up front to shorten review cycles.
Case topic · not in the main 20
Docs & knowledge flow
Single-page topic Aligns with skills “Docs” + case Engineering/Product
Overview: unify long-form design docs, runbooks, and knowledge bases for search, review, and onboarding; agents draft, cross-link, and flag staleness. When integrated with wikis or Git repos, declare authoritative sources and owners; when decisions change, point to replacement docs or ADR IDs. Prefer title prefixes, tags, and expiry dates for stale scans; separate internal from external-facing docs to avoid leaking sensitive architecture.
Relationship to the case hub: there is no standalone “Docs” category; related content lives in Engineering & architecture (e.g. CI/CD notes and release changelog generation), Product & UX (requirements and copy structure), and Industry & knowledge (notes and outlines). For broader documentation skills, see Skills · Docs & knowledge engineering.
Implementation notes (single page)
Archive and redirects
Move rather than delete stale pages; leave redirects or “superseded by” notes to avoid broken links and dual truths.
Trigger and exit (example)
Trigger: new RFC or doc past a staleness threshold. Output: outline + open questions. Exit: reviewed and merged to main or published to KB.