repo-diagram-planner

Plan source-grounded diagram tasks from repository evidence and specialist findings.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill repo-diagram-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-diagram-planner
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/repo-diagram-planner
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill repo-diagram-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill enables teams to turn scattered repository-evidence into bounded diagram tasks for architecture reviews, enabling faster, traceable diagram planning without authoring visuals.

Core Features & Use Cases

  • Integrates CodeBuddy review artifacts, specialist findings, and docs evidence to generate focused diagram tasks.
  • Produces a source-bound plan that maps evidence to diagram candidates and handoff notes to the diagram-author.
  • Supports plan-from-packet, plan-from-specialist-artifacts, plan-from-path, and refresh scenarios to keep planning aligned with current evidence.

Quick Start

Create a bounded repository packet with completed evidence and run the planner to emit a repo_diagram_plan artifact.

Frequently Asked Questions about repo-diagram-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan architecture diagrams from repository code and review evidence?

You can plan architecture diagrams from repository evidence by feeding bounded review packets containing repo paths and specialist findings into a planner, which outputs source-grounded diagram task briefs and an evidence map.

What is a source-grounded diagram task brief for code reviews?

A source-grounded diagram task brief is a planning artifact that maps repository evidence and specialist findings to specific diagram candidates, providing handoff notes for a diagram author without rendering the actual visuals.

How do I generate diagram tasks from CodeBuddy review artifacts and docs?

To generate diagram tasks from CodeBuddy review artifacts, you integrate completed evidence packets and specialist findings into the planner, which then emits a repo_diagram_plan artifact with mapped evidence and handoff instructions.

Can I use repository diagram planning for bounded review packets with a repo root?

Yes, repository diagram planning is designed specifically for bounded review packets containing a repo_root or explicit path documentation, especially when specialist artifacts are available to inform the diagram task generation.

Does diagram planning support refreshing tasks when repository evidence changes?

Yes, the plan-from-specialist-artifacts and refresh scenarios allow you to update diagram planning tasks so they stay aligned with the current repository evidence and latest specialist findings.

What are the limitations of planning diagrams from repository evidence without rendering visuals?

This approach focuses solely on producing non-rendered planning artifacts and evidence mappings, meaning it does not generate actual visual diagrams but instead creates bounded task briefs for a separate diagram author.