القائمة
Explore unfamiliar code and produce a written map. Use when the user wants to understand a new area, map modules and callers, or get a higher-level view before planning a change.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Ask which skill or flow fits your situation. A router over the skills in this repo.
Implement a piece of work based on a spec or set of tickets.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
| name | explore |
| description | Explore unfamiliar code and produce a written map. Use when the user wants to understand a new area, map modules and callers, or get a higher-level view before planning a change. |
Map relevant modules and callers at higher abstraction using multi-dimension working memory. Use the project's domain glossary vocabulary.
Before broad reads, locate relevant files/symbols with Glob, Grep, or targeted Read.
Prefer targeted Read with line ranges or block reads once the relevant area is known.
Read full files only when structure, ordering, or surrounding context is required for correctness.
Do not re-read unchanged files; use prior findings unless the file changed.
Start with Glob and Grep to identify directory structure and key patterns. Read representative files and key entrypoints, not every file in the area.
Initialize session: .scratch/explorations/<YYYY-MM-DD>/zoo-explore-<slug>/
Write <session-dir>/session.md with target area, scope, user request.
Map to <session-dir>/architecture.md:
Read <session-dir>/architecture.md for context.
Map to <session-dir>/data-flow.md:
Cross-reference architecture modules.
Read architecture and data-flow files.
Map to <session-dir>/call-graph.md:
Cross-reference previous dimensions.
Read all dimension files.
Write <session-dir>/synthesis.md:
Write the exact file path to .scratch/LAST-EXPLORATION.md so next commands can find it.
COMPLETION PROTOCOL: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
<session-dir>/synthesis.md path