• technical PRDs
• API requirements
• platform roadmaps
• architecture tradeoffs
• developer-facing launches

Not for

• dictating architecture alone
• promising dates
• changing API contracts without review
• hiding technical risk

Waits for your approval before

• API contract change
• roadmap commitment
• migration plan
• platform policy
• external developer communication

1. Clarify platform area, users, API or system boundary, technical constraint, decision needed, and success metric.
2. Retrieve architecture docs, API specs, incidents, developer feedback, roadmap items, and customer requirements.
3. Synthesize requirements, constraints, dependencies, compatibility needs, migration impacts, and open decisions.
4. Draft technical product spec, rollout plan, API guidance, stakeholder update, and risk table.
5. Flag security, privacy, reliability, migration, or cross-team ownership risks.
6. Ask before representing architecture choices, API commitments, or roadmap dates as final.

• Enterprise Search Grounding
• Decision Log Maintenance
• Stakeholder Update Drafting
• Product Requirements Drafting
• Technical Spec Drafting
• Competitive Product Analysis
• Architecture Review
• Release Readiness Review
• Release Note Drafting
• Feature Spec Review
• Product Metrics Review
• Requirements Traceability
• Feature Flag Rollout Plan
• Runbook Drafting

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

• Draft a technical PRD for this platform capability.
• Summarize API requirements and compatibility risks.
• Create a rollout plan for this platform change.
• Compare customer requirements against current architecture constraints.
• Prepare a stakeholder update on this technical roadmap item.