Documentation and Publishing Agents — Phase 9¶

Two paired agent flows backed by a shared, extensible skill architecture, so that any project's outputs can be turned into multi-format content and (optionally) published through approved external venues.

Pair¶

Documentation Agent — content generation and refinement.
Publishing Agent — channel-specific packaging and external delivery.

Shared skill architecture¶

┌───────────────────────┐
│  doc-skill-core       │  understand the project; extract sources; build a
│                       │  canonical content brief with citations.
└──────────┬────────────┘
           │
           v
┌───────────────────────┐         ┌───────────────────────┐
│  doc-format-adapters  │  -----> │  publication-adapters │
│                       │         │                       │
│  (technical | article │         │  (markdown-export    │
│   curriculum | video  │         │   | medium | youtube  │
│   ...)                │         │   | docsite | ...)    │
└───────────────────────┘         └───────────────────────┘

New content type = new file under templates/ + new entry in schemas/content-type.schema.json.
New venue = new adapter conforming to schemas/venue-adapter.schema.json.
Existing workflows do not change.

Files¶

File	Purpose
`schemas/content-type.schema.json`	Normalized doc-output schema.
`schemas/venue-adapter.schema.json`	Contract for publication destinations.
`policies/editorial-policy.md`	Voice, citation, safety.
`policies/publishing-policy.yaml`	Approval, environments, scopes.
`templates/technical-doc.template.md`	Technical doc baseline.
`templates/narrative-article.template.md`	Long-form article.
`templates/curriculum-module.template.md`	Curriculum lesson.
`templates/video-script.template.md`	Video script.
`workflows/doc-generation-loop.md`	Source → draft → review → finalize.
`workflows/publish-loop.md`	Finalize → package → dry-run → publish.
`runbooks/add-new-content-type.md`	Expand format model.
`runbooks/add-new-venue-adapter.md`	Expand venue model.
`audit/publish-audit-log-spec.md`	Lineage + publish events.

Ownership¶

Artifact	Owner
`content-type.schema.json` and templates	documentation
`venue-adapter.schema.json` and `publish-loop.md`	platform
`editorial-policy.md`	documentation + communications
`publishing-policy.yaml`	security + compliance
`runbooks/*`	operations
`publish-audit-log-spec.md`	compliance

Incremental rollout¶

Publish content-type.schema.json and technical-doc.template.md; generate one internal technical doc.
Add editorial-policy.md; run one quality review pass and revise output.
Add narrative-article.template.md and video-script.template.md; generate two additional content types from the same project source.
Add venue-adapter.schema.json and publishing-policy.yaml; execute one dry-run publish with no external side effects.
Add one real venue adapter and run one approval-gated publish; validate audit logs against publish-audit-log-spec.md.

Acceptance¶

One project context can produce multiple documentation types without manual re-authoring from scratch.
All outputs pass editorial policy checks before finalization.
No publish action occurs without policy-required approval.
New content types and venues can be added through adapters without redesigning core workflows.
Publish and rollback events are fully auditable.