conveyor-docs-steward

name	conveyor-docs-steward
description	Stewards Conveyor repo documentation so roadmap, handoff, changelog, ADRs, backlog docs, and domain language stay consistent without doc churn. Use when work changes Conveyor product direction, artifact boundaries, roadmap phase, session handoff state, completed product-level capabilities, or when asked to update docs.

Conveyor Docs Steward

Use this skill to decide which Conveyor docs must change after meaningful work. Do not mechanically update every doc. Preserve source-of-truth boundaries.

Source Of Truth

Read these first:

1. CONTEXT.md
2. docs/ROADMAP.md
3. docs/HANDOFF.md
4. docs/CHANGELOG.md
5. docs/conveyor-artifacts-v0.md
6. docs/agents/backlog.md
7. docs/adr/

CONTEXT.md wins for terminology. Current V4 language is: Intent, Plan, Slice, Agent Brief, Context Scout, Context Pack, Readiness, Run Prompt, Agent Run, Evidence, Run Dossier, Run Ledger, Review, Memory Candidate, Memory, Policy.

Do not reintroduce Work Order, factory framing, or vibe-coder framing as current product language unless the human explicitly reopens that decision.

Docs Impact Matrix

Update only the docs whose facts changed:

• Domain language or artifact relationship changed -> update CONTEXT.md.
• Architecture or product boundary decision changed -> add/update docs/adr/.
• Execution order, current phase, or next Slices changed -> update docs/ROADMAP.md.
• Next-session orientation, current status snapshot, or immediate next Slices changed -> update docs/HANDOFF.md.
• Product-level capability completed -> update docs/CHANGELOG.md.
• Backlog structure, triage vocabulary, or issue conventions changed -> update docs/agents/backlog.md or docs/agents/triage-labels.md.
• A PRD or implementation Slice changed -> update the relevant docs/backlog/<prd-slug>/... files.
• Run outcome or evidence changed -> update the relevant Run Dossier / Run Ledger, not the roadmap by default.
• Durable lesson discovered -> create or update Memory Candidate / Memory, not docs/HANDOFF.md by default.

Full Stewardship Workflow

Use when explicitly invoked for docs stewardship:

1. Recall ICM context for Conveyor docs decisions.
2. Run go run ./cmd/conveyor status.
3. Run go run ./cmd/conveyor backlog check.
4. Read the changed files or completed work summary.
5. Apply the docs impact matrix.
6. Edit only the docs with changed source-of-truth facts.
7. Scan edited docs for rejected or historical terminology.
8. Run go test ./... when code changed; otherwise run status and backlog checks at minimum.
9. Store an ICM summary when docs decisions or significant docs updates are completed.

Lightweight Closeout Check

Use after meaningful Conveyor work even when not explicitly invoked:

1. Did domain language change?
2. Did an architecture or artifact-boundary decision change?
3. Did roadmap phase, current focus, or next Slices change?
4. Did handoff-critical state change?
5. Was a product-level capability completed?
6. Did backlog conventions change?
7. Did Run Dossier, Run Ledger, Memory, or Policy state change?

If every answer is no, do not update continuity docs.

Guardrails

• Changelog and handoff are supporting continuity docs, not core Conveyor artifacts.
• Backlog is workflow scaffolding, not a core Conveyor artifact family.
• Do not duplicate detailed proof from PRDs, issues, Run Dossiers, Run Ledgers, commits, or conveyor status.
• Prefer concise factual updates over narrative history.
• If docs disagree, fix the downstream doc or flag the conflict before editing.