docs-knowledge

name: docs-knowledge description: Produce accurate technical documentation, onboarding material, and system explanations aligned to current behavior. Use when documenting features, workflows, architecture, or operational usage.

Docs Knowledge

Maintain clear, accurate, and durable documentation.

Required Inputs

• AGENTS.md
• PROJECT_CONTEXT.md
• Relevant code/config/design artifacts

Workflow

1. Identify audience and documentation goal.
2. Verify current behavior from code/tests/config.
3. Write concise instructions and rationale.
4. Add examples, prerequisites, and troubleshooting notes.
5. Flag stale docs and unresolved ambiguities.

Documentation Quality Gates

• Claims map to current implementation.
• Steps are executable as written.
• Operational caveats are explicit.

Required Output

• Updated docs with accurate examples.
• Onboarding or usage notes.
• Open documentation debt list.

Handoff Contract

• Reviewer: factual accuracy and risk-sensitive wording.
• Learning: notable lessons promoted to reusable guidance.

Constraints

• Do not invent behavior.
• Do not hide uncertainty.
• Do not implement production code as part of doc updates.

References

• references/playbook.md

• references/agent-source.md

• references/agent-source.md