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.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Google ADK (Agent Development Kit) orchestration patterns — boundaries, agent composition, and tool seams. Trigger when designing or reviewing multi-agent systems built on ADK. Authoritative source: adk.dev.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
JP's signature red-team pass — "how would I break this?" Argue against your own approach before proceeding. Trigger on any high-stakes decision, architecture choice, or before marking work complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read-only SRE checkup of any GCP project: deterministic probes of the edge, Cloud Run services, 7-day error logs, Cloud Scheduler, alert policies and uptime checks, Secret Manager and IAM, the data stores and the machine's own scheduled jobs, audited into one fixed status table (LIVE / WARNING / RED / INCONCLUSIVE) with evidence, findings by severity, what could not be checked, and a single OVERALL line delivered as one notification. Parametrised by a per-project manifest, so the same routine runs on every project. Use when the operator says "cloud checkup", "SRE check", "is everything live", "what's healthy / warning / red", "any errors this week", "audit the infra", "weekly checkup", "set up the weekly checkup", before a deploy or demo, or after an incident. Cloud Run first; App Engine and GKE differ only in the serving probes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cloud guardrails for any vendor workload — Google Cloud (GCP, Vertex AI, GKE), AWS (IAM, EKS, Bedrock), Azure (Entra ID, Policy, AKS), Alibaba Cloud (RAM, mainland/international residency). Enforces identity least-privilege, mechanical policy, data boundaries, residency, cost caps, network egress and observability, with official-source validation before any claim. Trigger on any cloud infrastructure design, review, Terraform plan, or LLM/agent deployment; the-architect routes here.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
LLM and cloud cost awareness — model tiering, token budgets, right-sizing, and when a cheaper model suffices. Trigger before finalising any architecture that calls LLMs, before scaling a workload, or when a cost estimate is needed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Challenge vision alignment, value, cost, risk and operating ownership at material scope or release decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.