菜单
RETIRED — the CozoDB graph backend (the graph-describe/graph-find-* shell wrappers) is permanently gone. Use the codegraph MCP tools instead for symbol/caller/callee/impact queries. Trigger with /graph-query. Loaded by ai-maestro-plugin
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Batch-approve, refuse, or archive TRDD proposals — move them between the four design/ zones (proposals/ to tasks/ on approve; to refused/ on refuse; to archived/ on complete/cancel/supersede). GATED: only a MANAGER (or solo USER) may approve/refuse/archive; the COS relays but does not approve; list is open to all. Use when a MANAGER drains the proposal queue or archives a finished/cancelled/superseded TRDD. Trigger with /ama-proposal-approvals, 'list pending proposals', or 'approve proposals 4,6'. Column moves within tasks/ are /ama-trdd-transition.
Search, read, verify, and server-mediated mutate TRDDs via the aimaestro-trdd.sh CLI — the AI Maestro dashboard's authorization-aware view of the design/ corpus. Write verbs (edit / approve / refuse / promote / archive) are STRICT, gated by each TRDD's min-approval-requirement with a hard self-approval ban. Use when server-mirrored state or server-side authorization matters: the dashboard kanban, approving a proposal, confirming an approval is real. Trigger with /ama-trdd-server, 'approve this TRDD', 'search TRDDs on the dashboard'. For local design/ file editing use ama-trdd-find/write/update/transition. Loaded by ai-maestro-plugin
Move a TRDD between kanban columns (the 14-stage pipeline plus blocked/failed) — enforcing the transition matrix: who may trigger each move, the frontmatter side-effects it requires, and the AMP broadcast it sends. Each move is role-gated (ORCH dispatches, ARCH designs, INTEGRATOR owns the ->complete flip, assignee signals dev->testing, MEMBER is signal-only). Use when advancing a task through the pipeline. Trigger with /ama-trdd-transition, 'move TRDD X to testing', 'dispatch this task', or 'mark it blocked'. Authoring is /ama-trdd-write, editing /ama-trdd-update, rendering /ama-kanban-render.
Author a new TRDD task-design document under design/ with correct v2 frontmatter — uuid + timestamps, the right zone (tasks/ for a Tier-0 task written directly as 'planned'; proposals/ for a Tier-1/2/3 task needing approval), and a self-contained body. Allowed for every role (MEMBER via COS). Use when a non-trivial task, feature, or decision must be captured as a tracked spec, or a report's decision becomes a TRDD. Trigger with /ama-trdd-write, 'write a TRDD for X', or 'capture this as a task spec'. Finding is /ama-trdd-find, editing /ama-trdd-update, column moves /ama-trdd-transition.
Use when managing teams or governance titles. Trigger with /team-governance. Loaded by ai-maestro-plugin
Manage team kanban boards and tasks. Use when creating, moving, filtering, getting, or editing tasks. Trigger with /team-kanban. Loaded by ai-maestro-plugin
| name | graph-query |
| user-invocable | false |
| description | RETIRED — the CozoDB graph backend (the graph-describe/graph-find-* shell wrappers) is permanently gone. Use the codegraph MCP tools instead for symbol/caller/callee/impact queries. Trigger with /graph-query. Loaded by ai-maestro-plugin |
| allowed-tools | Read, Glob, Grep |
| metadata | {"author":"Emasoft","version":"3.0.0"} |
This skill used to wrap a family of shell scripts that queried an AI Maestro
CozoDB graph backend. That backend has been permanently removed — there
is no replacement CLI, and none is planned. Do not look for graph-describe,
graph-find-callers, graph-index-delta, or any sibling wrapper script; they
no longer exist anywhere.
For code-structure questions, reach for the codegraph MCP tools (present
whenever a project has .codegraph/ initialized — check with
codegraph_status):
| Old graph-backend command | codegraph MCP tool |
|---|---|
graph-describe <symbol> | codegraph_node (pass includeCode: true for source) |
graph-find-callers <fn> | codegraph_callers |
graph-find-callees <fn> | codegraph_callees |
graph-find-path <from> <to> | codegraph_trace — one call returns the whole path, including dynamic-dispatch hops |
graph-find-related <sym> / graph-find-associations <sym> | codegraph_context (composes search + node + callers + callees in one call) |
graph-find-by-type <type> | codegraph_search (filter with kind) |
| survey several related symbols at once | codegraph_explore (one capped call instead of many codegraph_node/Read calls) |
| "what's in this directory" | codegraph_files |
| "what would break if I changed this" | codegraph_impact |
| re-index after a refactor | not needed — the file watcher keeps the index current (~500ms debounce behind writes) |
Rule of thumb: for "how does X work" / architecture / "what calls this" /
"what would break" questions, start with codegraph_context (broad survey) or
codegraph_trace (a specific flow from A to B) — both answer in 2-3 calls what
a grep+read loop would take dozens of calls to reconstruct.
If .codegraph/ is not initialized for the project, ask the user: "This
project doesn't have CodeGraph initialized — want me to run codegraph init -i
to build the index?"
Fall back to Grep/Glob/Read only for literal-text lookups (string
contents, log messages, comments) that codegraph cannot answer structurally.
None — this skill has no references/ anymore (the dead graph-backend docs
were removed). See the CodeGraph section of ~/.claude/rules/ for the full
tool-selection table, or ask codegraph_context/codegraph_search directly.
