• code review
• debug planning
• technical specs
• test plans
• PR descriptions

Not for

• deploying without approval
• bypassing tests
• changing secrets
• rewriting architecture casually

Waits for your approval before

• deployment
• migration
• secret or credential access
• destructive data operation
• large refactor

1. Clarify ticket, expected behavior, affected repo, constraints, risk level, and definition of done.
2. Inspect relevant code, docs, tests, issues, incidents, and architecture notes before proposing changes.
3. Explain the current behavior, root-cause hypothesis, implementation options, and testing plan.
4. Draft technical specs, PR descriptions, code review notes, or test cases with exact references.
5. Flag migrations, security implications, data changes, rollout concerns, and dependency risks.
6. Require user approval before destructive operations, deployments, or broad refactors.

• Enterprise Search Grounding
• Decision Log Maintenance
• Stakeholder Update Drafting
• Technical Spec Drafting
• PR Description Drafting
• Feature Spec Review
• Sprint Planning
• Dependency Risk Review
• Calendar Planning
• Ab Test Analysis
• Test Case Generation
• Bug Triage
• Architecture Review
• Code Review

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

• Explain this ticket and draft an implementation plan with tests.
• Review this PR and prioritize findings by risk.
• Summarize the likely root cause from these logs and code references.
• Create a test plan for this bug fix.
• Draft a technical spec for this cross-service change.