agdr

Index and query AgDR markdown files across projects with YAML frontmatter.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill agdr-aabdulghany
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agdr
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/agdr
Command: npx skills add https://github.com/AAbdulghany/fms --skill agdr-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly surface prior decisions by indexing AgDRs across every managed project, enabling fast recall and cross-project visibility.

Core Features & Use Cases

  • Portfolio-wide AgDR index and category-based browse
  • Full-text search across AgDR bodies and quick show-by-id lookup
  • Category statistics and per-project view to support planning and governance
  • Use Case: when you need to confirm whether a decision exists in another project before proceeding

Quick Start

Ask to browse or search AgDRs across the portfolio.

Frequently Asked Questions about agdr

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

FAQPage Schema
How do I search for past decisions across multiple projects?

You can search past decisions across multiple projects by indexing AgDR markdown files from local repositories or via API, parsing YAML frontmatter, and querying the built portfolio index.

What is an AgDR and when do I need to browse decision records?

An AgDR is a markdown decision record file with YAML frontmatter. You need to browse decision records when confirming whether a prior architectural choice exists before proceeding with new work.

Can I retrieve AgDRs from remote repositories via API?

Yes, you can retrieve AgDRs from remote repositories via API. The tool reads docs/agdr markdown files from each project either locally or through API integration.

How do I compute statistics on decision categories across a portfolio?

Compute statistics on decision categories by parsing YAML frontmatter from indexed AgDR files to aggregate category metadata, then generating per-category counts across the portfolio.

Do I need to manually refresh the AgDR index after updating decision records?

No, you do not need to manually refresh the AgDR index after updating decision records because the tool supports per-session caching and provides a --no-cache flag to force a refresh.

Best way to look up a specific decision record by ID?

The best way to look up a specific decision record by ID is using the quick show-by-id lookup feature after the portfolio AgDR index has been built and cached.