list-rfcs

List all RFCs with status, progress, and metadata

9 stars

Best use case

list-rfcs is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

List all RFCs with status, progress, and metadata

Teams using list-rfcs should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/list-rfcs/SKILL.md --create-dirs "https://raw.githubusercontent.com/jpoutrin/product-forge/main/plugins/devops-data/skills/list-rfcs/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/list-rfcs/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How list-rfcs Compares

Feature / Agentlist-rfcsStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

List all RFCs with status, progress, and metadata

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# list-rfcs

**Category**: Technical Architecture

## Usage

```bash
/list-rfcs [options]
```

## Options

| Option | Description |
|--------|-------------|
| `--status <status>` | Filter by status (DRAFT, REVIEW, APPROVED, IN_PROGRESS, COMPLETED) |
| `--all` | Include archived RFCs |
| `--author <name>` | Filter by author |
| `--format table|list` | Output format (default: table) |

## Execution Instructions

When this command is run, Claude Code should:

1. **Scan RFC Directories**
   ```
   rfcs/
   ├── draft/           → DRAFT
   ├── review/          → REVIEW
   ├── approved/        → APPROVED
   │   └── in-progress/ → IN_PROGRESS
   ├── completed/       → COMPLETED
   └── archive/         → (only with --all)
   ```

2. **Extract Metadata from Each RFC**
   - RFC ID (from filename or frontmatter)
   - Title
   - Status
   - Author
   - Created date
   - Last updated date
   - Reviewers and their status

3. **Apply Filters** (if specified)
   - Filter by status
   - Filter by author
   - Exclude archive unless `--all`

4. **Display Results**

### Table Format (default)

```
RFC Management Summary
======================

Active RFCs: 5 | In Review: 2 | Completed: 12

| RFC ID    | Title                      | Status      | Author    | Updated    |
|-----------|----------------------------|-------------|-----------|------------|
| RFC-0045  | API Gateway Selection      | REVIEW      | Jane Doe  | 2025-12-05 |
| RFC-0044  | Cache Strategy             | IN_PROGRESS | John Doe  | 2025-12-04 |
| RFC-0043  | Auth Redesign              | APPROVED    | Jane Doe  | 2025-12-01 |
| RFC-0042  | Database Migration         | DRAFT       | Bob Smith | 2025-11-28 |
| RFC-0041  | Logging Architecture       | DRAFT       | Jane Doe  | 2025-11-25 |

Use '/rfc-status RFC-XXXX' to see details or update status.
```

### List Format

```
RFC-0045: API Gateway Selection
  Status: REVIEW
  Author: Jane Doe
  Created: 2025-12-01
  Updated: 2025-12-05
  Reviewers: Alice (approved), Bob (pending)
  Location: rfcs/review/RFC-0045-api-gateway-selection.md

RFC-0044: Cache Strategy
  Status: IN_PROGRESS
  Author: John Doe
  ...
```

## Status Summary

Always show a summary at the top:

```
RFC Status Summary
==================
DRAFT:       3
REVIEW:      2
APPROVED:    1
IN_PROGRESS: 2
COMPLETED:   12
ARCHIVED:    8 (use --all to include)
```

## Sorting

Default sort order:
1. REVIEW (needs attention)
2. IN_PROGRESS
3. APPROVED
4. DRAFT
5. COMPLETED

Within each status, sort by last_updated (newest first).

## Example Usage

```bash
# List all active RFCs
/list-rfcs

# List only RFCs in review
/list-rfcs --status REVIEW

# List all including archived
/list-rfcs --all

# List RFCs by specific author
/list-rfcs --author "Jane Doe"
```

## Empty State

If no RFCs exist:

```
No RFCs found.

To create a new RFC:
  /create-rfc <title>

RFC documentation:
  See plugins/devops-data/skills/rfc-specification/SKILL.md
```

## Error Handling

- If `rfcs/` directory doesn't exist, show empty state message
- If RFC file has invalid frontmatter, show warning but continue
- Handle missing metadata gracefully (show "N/A")

Related Skills

task-list

9
from jpoutrin/product-forge

List tasks by directory with progress and visual indicators

list-qa-tests

9
from jpoutrin/product-forge

List QA test procedures with status and priority

list-tech-specs

9
from jpoutrin/product-forge

List all Technical Specifications with status and metadata

zod

9
from jpoutrin/product-forge

Zod schema validation patterns and type inference. Auto-loads when validating schemas, parsing data, validating forms, checking types at runtime, or using z.object/z.string/z.infer in TypeScript.

typescript-import-style

9
from jpoutrin/product-forge

Merge-friendly import formatting (one-per-line, alphabetical). Auto-loads when writing TypeScript/JavaScript imports to minimize merge conflicts in parallel development. Enforces consistent grouping and sorting.

setup-mcp-auth

9
from jpoutrin/product-forge

Configure authentication for an existing FastMCP server

fastmcp

9
from jpoutrin/product-forge

FastMCP TypeScript framework patterns for MCP servers. Auto-loads when building MCP servers, creating tools/resources/prompts, implementing authentication, configuring transports, or working with FastMCP in TypeScript.

add-mcp-tool

9
from jpoutrin/product-forge

Add a new tool to an existing FastMCP server with guided configuration

add-mcp-resource

9
from jpoutrin/product-forge

Add a new resource or resource template to an existing FastMCP server

plan-with-team

9
from jpoutrin/product-forge

Validate plan file ownership

privacy-compliance

9
from jpoutrin/product-forge

GDPR, CCPA, and privacy compliance guidance for data protection. Use when handling personal data, implementing consent management, or ensuring regulatory compliance across jurisdictions.

oauth

9
from jpoutrin/product-forge

OAuth 2.0 and OpenID Connect implementation patterns. Use when implementing authentication, authorization flows, or integrating with OAuth providers like Google, GitHub, or custom identity providers.