adk-expert
Google ADK (Agent Development Kit) orchestration patterns — boundaries, agent composition, and tool seams. Trigger when designing…
Maintain vision, user journeys, evolving requirements and roadmap outcomes when intent or acceptance changes.
Claude Code
$ npx -y skills add jpantsjoha/ai-native-developer-experience --skill product-owner --agent claude-code
Codex
$ npx skills add jpantsjoha/ai-native-developer-experience --skill product-owner -a codex -y
Cursor
$ npx skills add jpantsjoha/ai-native-developer-experience --skill product-owner -a cursor -y
Gemini CLI
$ npx skills add jpantsjoha/ai-native-developer-experience --skill product-owner -a gemini-cli -y
GitHub Copilot
$ npx skills add jpantsjoha/ai-native-developer-experience --skill product-owner -a github-copilot -y
OpenCode
$ npx skills add jpantsjoha/ai-native-developer-experience --skill product-owner -a opencode -y
Windsurf
$ npx skills add jpantsjoha/ai-native-developer-experience --skill product-owner -a windsurf -y
name: product-owner description: Maintain vision, user journeys, evolving requirements and roadmap outcomes when intent or acceptance changes.
Read the project vision, relevant requirements and current roadmap. Capture new intent with provenance and stable IDs; separate source wording from interpretation. Define the user journey, outcome, exclusions and observable acceptance. Check both directions: each promised journey has requirements, and each requirement serves a vision outcome.
Own the product content and roadmap priorities; the accountable human accepts material scope changes. Preserve accepted/superseded revisions and link changed business workflows and ADRs. Hand accepted requirements to delivery-orchestrator for ticket decomposition, sizing, assignment and state tracking. Do not duplicate its backlog.
At completion compare actual behaviour and test evidence with the accepted requirement, including reachability by the intended user. Record remaining coverage and acceptance explicitly; do not close a whole requirement because one implementing ticket merged.
**Shared ways of working for you, your team and your AI agents — from a new idea to a change running live.** join-the-team brings planning, delivery and ticket management, model selection, testing, independent review and release practices into one reusable
Google ADK (Agent Development Kit) orchestration patterns — boundaries, agent composition, and tool seams. Trigger when designing…
JP's signature red-team pass — "how would I break this?" Argue against your own approach before proceeding. Trigger on any…
Read-only SRE checkup of any GCP project: deterministic probes of the edge, Cloud Run services, 7-day error logs, Cloud…
Cloud guardrails for any vendor workload — Google Cloud (GCP, Vertex AI, GKE), AWS (IAM, EKS, Bedrock), Azure (Entra ID, Policy,…
LLM and cloud cost awareness — model tiering, token budgets, right-sizing, and when a cheaper model suffices. Trigger before…
Challenge vision alignment, value, cost, risk and operating ownership at material scope or release decisions.
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.