# Generate AGDT Framework Overview (Stakeholder Documentation)

You are generating **stakeholder-facing documentation about the Agentic
Development Tools (AGDT) framework** for a specific audience and occasion.

This prompt is **parameterised** — it produces the same well-structured overview
each time, retargeted via the three inputs below. Fill them in (or let the caller
substitute them) and follow the instructions to produce the deliverables.

---

## Inputs

| Variable | Meaning |
|----------|---------|
| `audience` | Who the documentation is for (their role, prior knowledge, what they care about). |
| `meeting_context` | The occasion / brief — meeting description, goal of the exchange, any framing to align with. |
| `emphasis` | What to foreground for this audience (the angles/messages to prioritise). |

### This run

**Audience:**

{{audience}}

**Meeting / context:**

{{meeting_context}}

**Emphasis for this run:**

{{emphasis}}

---

## What to Produce

Create **two Markdown files in `docs/temp/`** (do not overwrite unrelated files):

1. **`agdt-framework-overview.md`** — the comprehensive overview.
2. **`agdt-meeting-onepager.md`** — a condensed, presentation-ready one-pager that
   links back to the overview.

> **Note:** `docs/temp/` may not exist on a fresh checkout — create it with
> `mkdir -p docs/temp` before writing the output files.
>
> `docs/temp/` is a scratch location. If the output should be durable (e.g. moved
> to Confluence or committed), say so explicitly and place it accordingly.

## Ground the Content in the Repository (do not invent capabilities)

Before writing, gather facts from the actual codebase so claims are accurate:

- Read `README.md`, `.github/copilot-instructions.md`, and `docs/` (especially the
  arc42 docs `01`–`11`, `docs/mcp-server.md`).
- Confirm real command names from `pyproject.toml` `[project.scripts]` and the
  `agentic_devtools/cli/**` modules before naming any `agdt-*` command.
- For any "future / roadmap" claim (e.g. LangGraph orchestration), verify it maps
  to something real (`agentic_devtools/orchestration/`, specs under `specs/`) and
  clearly label it as *planned* vs *shipped*.

## Required Structure — `agdt-framework-overview.md`

Lead with an **executive summary**, then add depth. Include (adapt ordering to
`emphasis`):

1. **Executive Summary** — one-line pitch + why it matters for the audience.
2. **The Problem We Are Solving** — before/after contrast.
3. **What AGDT Is (Current Status)** — architecture diagram, command families,
   flagship workflows that exist today.
4. **How We Work Today: The AGDT-Driven Development Cycle** — the issue→merge loop
   (tracker-agnostic; note the tracker actually in use), with a **mandatory
   human-in-the-loop review gate**, and the planned **LangGraph** orchestration
   direction (*manual → assisted → orchestrated*).
5. **The Convenience-Function Vision** — the growing catalogue (docs freshness,
   telemetry/App-Insights issue analysis, best-practice & agentic-readiness audits).
6. **Why Repo Hygiene & Copilot/VS Code Conventions Are Central** — repo setup
   quality is an *input* to agent output quality.
7. **Design Principles**.
8. **Organisational / Transformational Fit** — the operating-model angle, not just tech.
9. **Roadmap / Intention**.
10. **Key Messages** — tailored to `audience` and `emphasis`.

## Required Structure — `agdt-meeting-onepager.md`

A tight, skimmable condensation: 30-second pitch, problem→answer, what exists today,
the dev-cycle sketch, the convenience-function catalogue, repo-hygiene theme, the
organisational angle, and the handful of messages to land. Link to the overview.

## Diagram & Formatting Rules (learned conventions)

- Use **Mermaid** for rich diagrams and **ASCII** sketches where a simple, tooling-free
  visual is better (the one-pager should stay ASCII-only so it renders anywhere).
- For **every Mermaid diagram**, prepend this init directive so arrows and edge
  labels are visible on dark backgrounds:

  ```text
  %%{init: {'theme':'base', 'themeVariables': {'lineColor':'#cccccc', 'edgeLabelBackground':'#ffffff'}}}%%
  ```

- Prefer widely-supported diagram types (`graph`, `flowchart`). **Avoid `mindmap`** —
  it renders blank on many Mermaid versions; use a `graph LR` tree instead.
- Keep ASCII diagrams short per line so they don't overflow on slides.
- Use relative Markdown links between the two files.

## Confluence / Export Note

If the docs are destined for a wiki (e.g. Confluence), remember Mermaid does **not**
render natively there — either use a Mermaid macro/app or export each diagram to an
image. The ASCII one-pager migrates with zero friction.

## Finishing Up

- Verify all `agdt-*` command names and file paths you cite actually exist.
- Confirm each Mermaid diagram carries the init directive and uses a supported type.
- Summarise what you produced and where, and note any claims labelled *planned*.
