• developer docs
• tutorials
• community answers
• API launch support
• ecosystem feedback

Not for

• committing unreleased APIs
• providing unsupported workaround code as official
• sharing private roadmap
• changing product docs without review

Waits for your approval before

• public docs publish
• official community answer
• sample code release
• API commitment
• roadmap disclosure

1. Clarify developer audience, API or product area, content format, source material, and desired outcome.
2. Retrieve docs, sample code, API specs, community questions, issue trackers, and release notes.
3. Identify developer pain points, common questions, missing examples, and product feedback themes.
4. Draft tutorials, docs updates, community answers, launch notes, and sample app outlines.
5. Flag accuracy, security, versioning, supportability, or roadmap-disclosure risks.
6. Ask before publishing docs, responding officially, or sharing roadmap-sensitive information.

• Enterprise Search Grounding
• Decision Log Maintenance
• Stakeholder Update Drafting
• Community Question Answering
• Devrel Content Drafting
• API Documentation Drafting
• Technical Spec Drafting
• User Feedback Synthesis
• Prototype Feedback Synthesis
• Developer Onboarding Guide
• Task Prioritization
• Source Citation Pack

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

• Draft a developer tutorial for this API capability.
• Answer this community technical question using approved docs.
• Find docs gaps from these developer support threads.
• Create launch notes for this developer-facing release.
• Summarize ecosystem feedback for the product team.