personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
5bbcee06ac07111b9c498e51bc05e0c241c2b946
leo-claude-mktplace/plugins/projman/commands/rfc.md
lmiranda 5bbcee06ac fix(commands): wire dispatch files to real sub-command names via Skill tool 
All dispatch files referenced display names (e.g., `/doc audit`) that don't
correspond to real slash commands. Claude Code resolves commands by filename,
so `/doc audit` loads `doc.md` with $ARGUMENTS but never routes to `doc-audit.md`.

Changes:
- Updated 24 dispatch files with explicit Skill tool routing
- Added "Command to Invoke" column with plugin-prefixed names
- Added $ARGUMENTS matching for automatic routing
- RFC dispatch file uses inline handling (no separate command files)
- Updated COMMANDS-CHEATSHEET.md with invocation methods
- Updated MIGRATION-v9.md with command name mapping explanation

Affects: 25 dispatch files across 12 plugins (core, data, saas, ops, debug)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-02-08 21:04:24 -05:00

4.9 KiB
Raw Blame History

name, description, agent
name description agent
rfc RFC lifecycle management - create, list, review, approve, reject planner

RFC Management

Skills Required

  • skills/mcp-tools-reference.md
  • skills/rfc-workflow.md
  • skills/rfc-templates.md

Purpose

Manage the full RFC lifecycle through sub-commands. RFCs provide a structured way to document, discuss, and approve changes before implementation.

When invoked without a sub-command or with $ARGUMENTS, handle sub-commands inline using the documentation below.

Invocation

/rfc <sub-command> [arguments]

Available Commands

Command Usage Description
create /rfc create Create new RFC from conversation or clarified spec
list /rfc list [filter] List all RFCs grouped by status
review /rfc review <number> Submit Draft RFC for review
approve /rfc approve <number> Approve RFC in Review status
reject /rfc reject <number> Reject RFC with documented reason

Routing

If $ARGUMENTS is provided (e.g., user typed /rfc create):

  1. Match the first word of $ARGUMENTS against the Command column above
  2. Execute the corresponding sub-command using the inline documentation below
  3. Pass any remaining arguments to the sub-command handler

If no arguments provided:

  1. Display the Available Commands table
  2. Ask: "Which command would you like to run?"
  3. When the user responds, execute the matching sub-command using the inline documentation below

Note: RFC commands are handled inline in this file - there are no separate command files to invoke.

Sub-Command: create

Create a new RFC wiki page to track a feature idea through the review lifecycle.

Workflow:

  1. Check if conversation has clarified specification (from /clarity clarify)
  2. If no context: prompt for Summary, Motivation, and initial Design
  3. Call allocate_rfc_number MCP tool for next sequential number
  4. Create RFC page using template from skills/rfc-templates.md
  5. Update RFC-Index wiki page (create if doesn't exist)
  6. Display RFC number, wiki link, and next steps

Input Mapping (from /clarity clarify):

Clarify Section RFC Section
Problem/Context Motivation > Problem Statement
Goals/Outcomes Motivation > Goals
Scope/Requirements Detailed Design > Overview
Constraints Non-Goals or Detailed Design
Success Criteria Testing Strategy

Edge cases:

  • No RFC-Index exists: Create it with empty sections
  • User provides minimal input: Create minimal RFC template, note sections to fill
  • Duplicate title: Proceed (RFC numbers are unique, titles don't need to be)

Sub-Command: list

Display all RFCs grouped by lifecycle status.

Filters: /rfc list approved, /rfc list draft, /rfc list review

Workflow:

  1. Fetch RFC-Index wiki page via get_wiki_page
  2. Parse tables from each status section
  3. Display grouped by status, highlight Approved section
  4. Show counts per status

Edge cases:

  • No RFC-Index: "No RFCs yet. Create one with /rfc create"
  • Empty sections: Show "(none)"

Sub-Command: review

Submit a Draft RFC for review, transitioning status to Review.

Usage: /rfc review <number> (leading zeros optional)

Workflow:

  1. Validate RFC number, fetch page
  2. Check status is Draft - STOP if not
  3. Validate minimum content (Summary, Motivation, Detailed Design > Overview required)
  4. Optionally assign champion
  5. Update RFC page: status Draft -> Review, update date
  6. Update RFC-Index: move from Draft to In Review section

Sub-Command: approve

Approve an RFC in Review status for sprint planning.

Usage: /rfc approve <number> (leading zeros optional)

Workflow:

  1. Validate RFC number, fetch page
  2. Check status is Review - STOP if not
  3. Gather approval rationale (required)
  4. Update RFC page: status Review -> Approved, add Decision section
  5. Update RFC-Index: move from In Review to Approved section

Sub-Command: reject

Reject an RFC with documented reason.

Usage: /rfc reject <number> (leading zeros optional)

Workflow:

  1. Validate RFC number, fetch page
  2. Check status is Draft or Review - STOP if not
  3. Require rejection reason (mandatory)
  4. Update RFC page: status -> Rejected, add Decision section
  5. Update RFC-Index: move to Rejected section

Visual Output

+----------------------------------------------------------------------+
|  PROJMAN - RFC [Sub-Command]                                         |
+----------------------------------------------------------------------+

Validation Errors (All Sub-Commands)

  • RFC not found: "RFC-NNNN not found. Check the number with /rfc list"
  • Wrong status: "RFC-NNNN is in [status] status. [Specific allowed statuses for this action]."
  • Missing required input: Specific message per sub-command
  • No sub-command provided: Display sub-command reference table
Reference in New Issue View Git Blame Copy Permalink