novastorm-tracker
Guide and recipes for managing Buganizer issues for the NovaStorm project (Component ID 2059327).
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Guide and recipes for managing Buganizer issues for the NovaStorm project (Component ID 2059327).
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | novastorm-tracker |
| description | Guide and recipes for managing Buganizer issues for the NovaStorm project (Component ID 2059327). |
Use this skill when managing Buganizer issues for the NovaStorm project. It provides recipes and default configurations to interact with the Buganizer MCP using the correct Component ID (2059327).
The default component ID for NovaStorm is 2059327.
Issues should have the following attributes:
NEW (if possible, otherwise ASSIGNED).jwortz@google.com).NovaStorm: Dynamic Swarm Intelligence (DSSIB) on Google Cloud.To set attributes automatically (if not supported by tool parameters), use comment commands in the initial description or a follow-up comment.
Using Comment Commands:
/status NEW/assign jwortz@google.com/planned-for "NovaStorm: Dynamic Swarm Intelligence (DSSIB) on Google Cloud"Note: Status might automatically become ASSIGNED if an assignee is present. Planned For may require manual setting if tools do not support it.
Use this recipe to list open bugs in the NovaStorm component.
# Using Buganizer MCP (conceptual example, use actual tool)
# query: "componentid:2059327 status:open"
Note: Since the Buganizer MCP tools require explicit parameters, use the following patterns.
Using mcp_buganizer_get_bugs Tool:
query: componentid:2059327 status:openmaxResults: 10 (default)Use this recipe to file a new bug in the NovaStorm component.
Using mcp_buganizer_create_buganizer_issue Tool:
componentId: "2059327"title: "[Category] Brief description"commentMarkdown: "Detailed description..."priority: "P2" (default)severity: "S2" (default)Search for specific text within the NovaStorm component.
Using mcp_buganizer_get_bugs Tool:
query: componentid:2059327 "search term"List issues related to Phase 3 implementation.
Using mcp_buganizer_get_bugs Tool:
query: componentid:2059327 "Phase 3"componentId: "2059327" when creating or listing issues for NovaStorm unless specifically directed otherwise.[GEPA], [Critic Agent], [Cloud Run], [Dataplex], [Multi-Agent], [Memory Bank], etc.Analyze agent session transcripts to find looping behavior, missing capabilities, or token waste, and leverage framework-native concepts and skill-creator patterns to propose optimizations.
Build multi-agent systems using Google ADK with A2A protocol, deployed on Agent Engine. Use when creating agents that communicate via A2A, building multi-tier agent hierarchies, connecting ADK agents with RemoteA2aAgent, exposing agents with to_a2a(), or deploying agent stacks to Vertex AI Agent Engine. Covers leaf agents with tools, functional agents that delegate, orchestrators that route, local testing with uvicorn, and phased cloud deployment.
Build AI agents using Google's Agent Development Kit (ADK). Use when creating LLM agents with tools, building workflow agents (Sequential, Parallel, Loop), composing multi-agent systems, or developing custom agents. Covers agent creation patterns, function tools, agent configuration, session management, and running agents locally with CLI or web interface.
Deploy and manage AI agents on Vertex AI Agent Engine. Use when deploying ADK agents to production, configuring Agent Engine runtime, managing deployed agents, setting up sessions and memory, or integrating with A2A protocol. Covers deployment from agent objects and source files, environment configuration, scaling, sessions, memory bank, and agent management operations.
Sprint-based agile development with parallel agent execution. Use when the user wants to run an agile sprint, plan sprint work, conduct standups, run retrospectives, manage a backlog, estimate story points, track velocity, or coordinate parallel development across multiple agents acting as Scrum team roles (Scrum Master, Product Owner, Tech Lead, Frontend Dev, Backend Dev, QA Engineer). Also use when the user mentions sprints, user stories, acceptance criteria, definition of done, kanban, or SAFe. Triggers on: 'run a sprint', 'sprint planning', 'standup', 'retrospective', 'backlog grooming', 'agile workflow', 'scrum team'.
Clarify requirements before implementing. Use when serious doubts araise.