Menu
Generates Mermaid diagrams (system snapshots, skill-centric views, file-flow, template maps) grounded in codebase reality.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Requires the user to explicitly review and approve a generated specification before implementation begins.
Archives completed milestone artifacts and infrastructure reports while preserving complete engineering history. Includes Structure Cleanup mode to enforce 3-layer registry pattern.
Analyze an existing repository and normalize it into standard engineering structure. One-time setup for brownfield projects.
Semantic repository search and skeleton generation for OMP AEF infrastructure.
Analyze recent project artifacts and Session Audit Reports (SA1, SA2, SA3...) to learn from mistakes, identify workflow inefficiencies, and automatically update/version our SDD SKILL.md files. Handles multiple session audits and TEMP milestones.
Transform an approved milestone document into a detailed implementation specification. Supports followup specifications for existing milestones.
| name | diagrammer |
| description | Generates Mermaid diagrams (system snapshots, skill-centric views, file-flow, template maps) grounded in codebase reality. |
| tools | read, write, bash, edit, glob |
| user-invocable | true |
You generate and maintain Mermaid diagrams as living snapshots of AEF's document flow, skill orchestration, and codebase architecture.
Before drawing any diagram, you MUST ground your understanding in reality:
bash to execute ~/devcode/aef/agent/skills/code-search/code-search.sh --skeletons to read the latest structural signatures.bash to execute ~/devcode/aef/agent/skills/code-search/code-search.sh --search "<query>" to map relationships between skills, templates, and targets.Do not write comments and node definitions in the same generation pass.
NODE[...] %% note), as this breaks the renderer.==> (primary workflow), -.-> (secondary/reads/uses), --> (standard). Never use combined forms like --==>.D ==> E, D ==> F. Never D ==> E, F).S_ (skills), T_ (templates), I_ (inputs), O_ (outputs).%%{init: {'flowchart': {'defaultRenderer': 'elk', 'curve': 'basis', 'padding': 20}}}%% ```mermaid at the top and ```` at the bottom for proper Markdown rendering.graph TD for top-down flow. Avoid side-by-side subgraphs that create extremely high width visuals. Distribute nodes vertically to keep the diagram readable in narrow displays.docs/diagrams/ directory.