list

List ADRs and specs with status and dates from YAML frontmatter.

30|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/joestump/claude-plugin-design --skill list-joestump
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: list
Source: https://github.com/joestump/claude-plugin-design/tree/main/skills/list
Command: npx skills add https://github.com/joestump/claude-plugin-design --skill list-joestump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discover and track the current status of architectural decisions (ADRs) and specifications (specs) across a codebase, reducing confusion and drift.

Core Features & Use Cases

  • Retrieve and display ADRs and specs with status, date, and title.
  • Filter results by ADRs, specs, or both to tailor reviews.
  • Present results in a clear table and gracefully handle empty results.

Quick Start

Run the list skill to see all ADRs and specs with their status.

Frequently Asked Questions about list

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

FAQPage Schema
How do I list all ADRs and specs with their current status in a project?

To list ADRs and specs with their status, this Skill reads YAML frontmatter from documents stored under docs/adrs and docs/openspec/specs. It parses titles from headings and dates from metadata, then presents the results in a formatted table.

What is the best way to track architectural decisions and specifications status across a codebase?

Tracking architectural decisions and specifications status is done by scanning docs/adrs and docs/openspec/specs directories. It extracts status and date values from YAML frontmatter to reduce documentation drift across your project.

Can I filter the output to show only ADRs or only specs?

Yes, you can filter the output to show only ADRs, only specs, or both. This allows you to tailor documentation reviews specifically to architectural decisions or specifications.

Does this tool work with ADR and spec files stored outside the docs/adrs and docs/openspec/specs directories?

No, it specifically applies to projects with ADRs and specs stored under docs/adrs and docs/openspec/specs. It requires these exact directory paths to read YAML frontmatter and parse document titles.

How does the tool handle empty results when no ADRs or specs are found?

When no ADRs or specs are found, it handles the empty results gracefully. The tool avoids throwing errors and simply presents an empty state instead of a formatted table.