菜单
How and when to query the repo's knowledge graph — find symbols, trace call chains, compute blast radius, map architecture. Use before grep for any structural code question — who calls this, what does X depend on, what breaks if this changes, what's the shape of this codebase.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
The Delivery Lead persona — owns HOW the team delivers and owns the rituals. Activate when the user has a team call to prepare or run (planning, refinement, standup, retro, review), asks what ritual or process fits, wants iterations or cadence set up, asks "what are we doing on this call", wonders how to get from backlog to built, or when delivery feels stuck or chaotic. A facilitator: it structures conversations where the TEAM supplies the content; it teaches what each ritual is when asked; it never mutates the board without an explicit go.
The Navigator persona — the guide over the whole Code Factory. Activate FIRST on any big or multi-part organizational prompt ("we need to organize this", "here are the repos, set up delivery", a pasted brief plus "where do we start"), when the user asks how to use these skills, what a term or ritual means, what state the work is in, or what the next step is. It reads the board, the repo, and the clock, then answers "here's where you are, here are the possible next moves" — it talks and routes; it NEVER executes work or mutates anything.
The Product Manager persona — owns WHAT gets built and in what order, and owns the board's contents. Activate when the user brings raw work to organize (a brief, a pile of tasks, "we need to sort this out"), asks what to build next, wants the backlog groomed, triaged, or prioritized, needs epics or a roadmap, or mentions tickets piling up. A conversation-first role: it proposes and asks; it never acts on the board without an explicit go.
Configure a repo for Code Factory — issue tracker, triage labels, domain docs, the company GitHub Project board, and the codebase-memory index. Run once per repo before any other Code Factory skill.
Establish what the team can actually take on — measured pace minus known absences and interrupt load, per person WIP checked, the number planning is allowed to spend.
Sweep the active work for dependencies and risks — blocking chains mapped, single points of failure named, each real risk given an owner and a trigger, theatre avoided.
基于 SOC 职业分类
| name | codebase-memory |
| description | How and when to query the repo's knowledge graph — find symbols, trace call chains, compute blast radius, map architecture. Use before grep for any structural code question — who calls this, what does X depend on, what breaks if this changes, what's the shape of this codebase. |
The bundled codebase-memory MCP holds a graph of this repo's code: functions, classes, routes, and the edges between them. For structural questions it answers in one call what grep approximates in ten — reach for the graph first, grep for raw text (strings, configs, comments) only.
docs/agents/codebase-memory.md says whether this repo is indexed. Not indexed → run index_repository first (or fall back to grep if the user declined indexing at setup).
| Question | Call |
|---|---|
| Where is this function/class/route? | search_graph (name_pattern / label / qn_pattern) |
| Who calls X? What does X call? | trace_path (mode=calls) |
| How does data flow through here? | trace_path (mode=data_flow, cross_service for seams) |
| Exact source of a symbol | get_code_snippet (qualified_name — precise ranges) |
| What breaks if I change X? | trace_path on X's callers + query_graph for dependents — the blast radius |
| What's the shape of this codebase? | get_architecture (aspects) |
| Anything relational the above can't say | query_graph (Cypher) |
| Text that isn't a symbol | search_code (graph-augmented grep) |
get_architecture for the map, trace_path to see how the affected flow actually runs today.The graph reflects the last index. After a large refactor or a long-running branch, detect_changes; rebuild with index_repository when drift is real. A symbol the graph can't find that plainly exists in the tree = stale index — reindex rather than distrusting the graph wholesale.