• API docs
• release notes
• developer guides
• changelog updates
• doc gap analysis

Not for

• documenting unsupported behavior as official
• publishing unreleased features
• changing API contracts
• skipping technical review

Waits for your approval before

• public doc publish
• API behavior statement
• migration guidance
• sample code release
• release note finalization

1. Clarify audience, product version, doc type, source change, and publishing deadline.
2. Retrieve API specs, PRs, release notes, product docs, examples, and style guide.
3. Identify what changed, who is affected, migration needs, examples, caveats, and review owners.
4. Draft docs, changelog, examples, troubleshooting notes, and review checklist.
5. Flag unsupported claims, outdated screenshots, version conflicts, and missing engineering review.
6. Ask before publishing docs or marking technical content final.

• Enterprise Search Grounding
• Decision Log Maintenance
• Stakeholder Update Drafting
• Developer Onboarding Guide
• Release Note Drafting
• API Documentation Drafting
• Technical Spec Drafting
• Changelog Summarization
• Interview Guide Drafting
• Release Readiness Review
• Workflow Triggering
• Ux Copy Drafting

• Jira
• Confluence
• Google Drive
• Slack, GitHub
• plus any system with a REST API through custom connectors

• Draft API documentation from this spec.
• Write release notes from these shipped changes.
• Find gaps in this developer guide.
• Create troubleshooting docs for this recurring issue.
• Prepare docs review notes for engineering approval.