refactor(projman): normalize RFC to sub-command pattern, absorb clear-cache
- Created unified /rfc command with create|list|review|approve|reject sub-commands - Deleted 5 individual rfc-*.md command files - Moved /clear-cache into /setup --clear-cache - Updated all cross-references in skills, docs, and integration files - Command count: 17 -> 12 (net -5) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
5
plugins/projman/.doc-guardian-queue
Normal file
5
plugins/projman/.doc-guardian-queue
Normal file
@@ -0,0 +1,5 @@
|
||||
2026-01-30T14:32:53 | skills | /home/lmiranda/claude-plugins-work/plugins/projman/skills/setup-workflows.md | README.md
|
||||
2026-01-30T14:32:53 | commands | /home/lmiranda/claude-plugins-work/plugins/projman/commands/setup.md | docs/COMMANDS-CHEATSHEET.md README.md
|
||||
2026-01-30T14:32:54 | commands | /home/lmiranda/claude-plugins-work/plugins/projman/commands/debug.md | docs/COMMANDS-CHEATSHEET.md README.md
|
||||
2026-01-30T14:32:54 | commands | /home/lmiranda/claude-plugins-work/plugins/projman/commands/test.md | docs/COMMANDS-CHEATSHEET.md README.md
|
||||
2026-01-30T14:33:13 | commands | /home/lmiranda/claude-plugins-work/plugins/projman/commands/sprint-status.md | docs/COMMANDS-CHEATSHEET.md README.md
|
||||
@@ -12,11 +12,11 @@ This project uses the **projman** plugin for sprint planning and project managem
|
||||
| `/sprint-close` | Complete sprint and capture lessons learned to Gitea Wiki |
|
||||
| `/labels-sync` | Synchronize label taxonomy from Gitea |
|
||||
| `/initial-setup` | Run initial setup for projman plugin |
|
||||
| `/rfc-create` | Create new RFC from conversation or clarified spec |
|
||||
| `/rfc-list` | List all RFCs grouped by status |
|
||||
| `/rfc-review` | Submit Draft RFC for review |
|
||||
| `/rfc-approve` | Approve RFC for sprint planning |
|
||||
| `/rfc-reject` | Reject RFC with documented reason |
|
||||
| `/rfc create` | Create new RFC from conversation or clarified spec |
|
||||
| `/rfc list` | List all RFCs grouped by status |
|
||||
| `/rfc review` | Submit Draft RFC for review |
|
||||
| `/rfc approve` | Approve RFC for sprint planning |
|
||||
| `/rfc reject` | Reject RFC with documented reason |
|
||||
|
||||
### MCP Tools Available
|
||||
|
||||
|
||||
@@ -1,34 +0,0 @@
|
||||
---
|
||||
description: Clear plugin cache to force fresh configuration reload after marketplace updates
|
||||
---
|
||||
|
||||
# Clear Cache
|
||||
|
||||
## Purpose
|
||||
|
||||
Clear plugin cache to force fresh configuration reload after marketplace updates.
|
||||
|
||||
## When to Use
|
||||
|
||||
- After updating the marketplace (`git pull` or reinstall)
|
||||
- When MCP servers show stale configuration
|
||||
- When plugin changes don't take effect
|
||||
|
||||
## Workflow
|
||||
|
||||
Execute cache clear:
|
||||
|
||||
```bash
|
||||
rm -rf ~/.claude/plugins/cache/leo-claude-mktplace/
|
||||
```
|
||||
|
||||
Then inform user: "Cache cleared. Restart Claude Code for changes to take effect."
|
||||
|
||||
## Visual Output
|
||||
|
||||
```
|
||||
╔══════════════════════════════════════════════════════════════════╗
|
||||
║ 📋 PROJMAN ║
|
||||
║ Clear Cache ║
|
||||
╚══════════════════════════════════════════════════════════════════╝
|
||||
```
|
||||
@@ -1,83 +0,0 @@
|
||||
---
|
||||
description: Approve an RFC in Review status, making it ready for sprint planning
|
||||
agent: planner
|
||||
---
|
||||
|
||||
# Approve RFC
|
||||
|
||||
## Skills Required
|
||||
|
||||
- skills/mcp-tools-reference.md
|
||||
- skills/rfc-workflow.md
|
||||
- skills/rfc-templates.md
|
||||
|
||||
## Purpose
|
||||
|
||||
Transition an RFC from Review to Approved status, indicating the proposal has been accepted and is ready for implementation in an upcoming sprint.
|
||||
|
||||
## Invocation
|
||||
|
||||
Run `/rfc-approve <number>` where number is the RFC number:
|
||||
- `/rfc-approve 0003`
|
||||
- `/rfc-approve 3` (leading zeros optional)
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Validate RFC Number**
|
||||
- Normalize input (add leading zeros if needed)
|
||||
- Fetch RFC page: `RFC-NNNN: *`
|
||||
|
||||
2. **Check Current Status**
|
||||
- Parse frontmatter to get current status
|
||||
- **STOP** if status is not "Review"
|
||||
- Error: "RFC-NNNN is in [status] status. Only RFCs in Review can be approved."
|
||||
|
||||
3. **Gather Decision Details**
|
||||
- Prompt: "Please provide the approval rationale (why is this RFC being approved?):"
|
||||
- This becomes the Decision section content
|
||||
|
||||
4. **Update RFC Page**
|
||||
- Change status: Review → Approved
|
||||
- Update "Updated" date
|
||||
- Add/update Decision section:
|
||||
```markdown
|
||||
## Decision
|
||||
|
||||
**Decision:** Approved
|
||||
**Date:** YYYY-MM-DD
|
||||
**Decided By:** @[current user or maintainer]
|
||||
|
||||
**Rationale:**
|
||||
|
||||
[User-provided rationale]
|
||||
```
|
||||
|
||||
5. **Update RFC-Index**
|
||||
- Remove entry from "## In Review" section
|
||||
- Add entry to "## Approved" section
|
||||
|
||||
6. **Confirm Approval**
|
||||
- Display updated status
|
||||
- Note that RFC is now available for `/sprint-plan`
|
||||
|
||||
## Visual Output
|
||||
|
||||
```
|
||||
+----------------------------------------------------------------------+
|
||||
| PROJMAN - RFC Approval |
|
||||
+----------------------------------------------------------------------+
|
||||
|
||||
RFC-0003: Feature X has been approved!
|
||||
|
||||
Status: Review → Approved
|
||||
Decision recorded in RFC page.
|
||||
|
||||
This RFC is now available for sprint planning.
|
||||
Use /sprint-plan and select this RFC when prompted.
|
||||
```
|
||||
|
||||
## Validation Errors
|
||||
|
||||
- **RFC not found**: "RFC-NNNN not found. Check the number with /rfc-list"
|
||||
- **Wrong status**: "RFC-NNNN is [status]. Only RFCs in Review can be approved."
|
||||
- **No rationale provided**: "Approval rationale is required. Please explain why this RFC is being approved."
|
||||
@@ -1,84 +0,0 @@
|
||||
---
|
||||
description: Create a new RFC (Request for Comments) from conversation or clarified specification
|
||||
agent: planner
|
||||
---
|
||||
|
||||
# Create RFC
|
||||
|
||||
## Skills Required
|
||||
|
||||
- skills/mcp-tools-reference.md
|
||||
- skills/rfc-workflow.md
|
||||
- skills/rfc-templates.md
|
||||
|
||||
## Purpose
|
||||
|
||||
Create a new RFC wiki page to track a feature idea, proposal, or enhancement through the review lifecycle. RFCs provide a structured way to document, discuss, and approve changes before implementation.
|
||||
|
||||
## Invocation
|
||||
|
||||
Run `/rfc-create` with optional context:
|
||||
- After `/clarify` to convert clarified spec to RFC
|
||||
- With description of feature idea
|
||||
- From conversation context
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Gather Input**
|
||||
- Check if conversation has clarified specification (from `/clarify`)
|
||||
- If no context: prompt for Summary, Motivation, and initial Design
|
||||
- Extract author from context or prompt
|
||||
|
||||
2. **Allocate RFC Number**
|
||||
- Call `allocate_rfc_number` MCP tool
|
||||
- Get next sequential 4-digit number
|
||||
|
||||
3. **Create RFC Page**
|
||||
- Use template from `skills/rfc-templates.md`
|
||||
- Fill in frontmatter (number, title, status=Draft, author, dates)
|
||||
- Populate Summary, Motivation, Detailed Design sections
|
||||
- Create wiki page: `RFC-NNNN: Title`
|
||||
|
||||
4. **Update RFC-Index**
|
||||
- Fetch RFC-Index (create if doesn't exist)
|
||||
- Add entry to "## Draft" section
|
||||
- Update wiki page
|
||||
|
||||
5. **Confirm Creation**
|
||||
- Display RFC number and wiki link
|
||||
- Remind about next steps (refine → `/rfc-review`)
|
||||
|
||||
## Visual Output
|
||||
|
||||
```
|
||||
+----------------------------------------------------------------------+
|
||||
| PROJMAN - RFC Creation |
|
||||
+----------------------------------------------------------------------+
|
||||
|
||||
RFC-0001: [Title] created successfully!
|
||||
|
||||
Status: Draft
|
||||
Wiki: [link to RFC page]
|
||||
|
||||
Next steps:
|
||||
- Refine the RFC with additional details
|
||||
- When ready: /rfc-review 0001 to submit for review
|
||||
```
|
||||
|
||||
## Input Mapping
|
||||
|
||||
When converting from `/clarify` output:
|
||||
|
||||
| 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)
|
||||
@@ -1,98 +0,0 @@
|
||||
---
|
||||
description: List all RFCs grouped by status from RFC-Index wiki page
|
||||
agent: planner
|
||||
---
|
||||
|
||||
# List RFCs
|
||||
|
||||
## Skills Required
|
||||
|
||||
- skills/mcp-tools-reference.md
|
||||
- skills/rfc-workflow.md
|
||||
|
||||
## Purpose
|
||||
|
||||
Display all RFCs grouped by their lifecycle status. Highlights "Approved" RFCs that are ready for sprint planning.
|
||||
|
||||
## Invocation
|
||||
|
||||
Run `/rfc-list` to see all RFCs.
|
||||
|
||||
Optional filters:
|
||||
- `/rfc-list approved` - Show only approved RFCs
|
||||
- `/rfc-list draft` - Show only draft RFCs
|
||||
- `/rfc-list review` - Show only RFCs in review
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Fetch RFC-Index**
|
||||
- Call `get_wiki_page` for "RFC-Index"
|
||||
- Handle missing index gracefully
|
||||
|
||||
2. **Parse Sections**
|
||||
- Extract tables from each status section
|
||||
- Parse RFC number, title, and metadata from each row
|
||||
|
||||
3. **Display Results**
|
||||
- Group by status
|
||||
- Highlight Approved section (ready for planning)
|
||||
- Show counts per status
|
||||
|
||||
## Visual Output
|
||||
|
||||
```
|
||||
+----------------------------------------------------------------------+
|
||||
| PROJMAN - RFC Index |
|
||||
+----------------------------------------------------------------------+
|
||||
|
||||
## Approved (Ready for Sprint Planning)
|
||||
|
||||
| RFC | Title | Champion | Created |
|
||||
|-----|-------|----------|---------|
|
||||
| RFC-0003 | Feature X | @user | 2026-01-15 |
|
||||
| RFC-0007 | Enhancement Y | @user | 2026-01-28 |
|
||||
|
||||
## In Review (2)
|
||||
|
||||
| RFC | Title | Author | Created |
|
||||
|-----|-------|--------|---------|
|
||||
| RFC-0004 | Feature Y | @user | 2026-01-20 |
|
||||
| RFC-0008 | Idea Z | @user | 2026-01-29 |
|
||||
|
||||
## Draft (3)
|
||||
|
||||
| RFC | Title | Author | Created |
|
||||
|-----|-------|--------|---------|
|
||||
| RFC-0005 | Concept A | @user | 2026-01-22 |
|
||||
| RFC-0009 | Proposal B | @user | 2026-01-30 |
|
||||
| RFC-0010 | Sketch C | @user | 2026-01-30 |
|
||||
|
||||
## Implementing (1)
|
||||
|
||||
| RFC | Title | Sprint | Started |
|
||||
|-----|-------|--------|---------|
|
||||
| RFC-0002 | Feature W | Sprint 18 | 2026-01-22 |
|
||||
|
||||
## Implemented (1)
|
||||
|
||||
| RFC | Title | Completed | Release |
|
||||
|-----|-------|-----------|---------|
|
||||
| RFC-0001 | Initial Feature | 2026-01-10 | v5.0.0 |
|
||||
|
||||
## Rejected (0)
|
||||
|
||||
(none)
|
||||
|
||||
## Stale (0)
|
||||
|
||||
(none)
|
||||
|
||||
---
|
||||
Total: 10 RFCs | 2 Approved | 1 Implementing
|
||||
```
|
||||
|
||||
## Edge Cases
|
||||
|
||||
- **No RFC-Index**: Display message "No RFCs yet. Create one with /rfc-create"
|
||||
- **Empty sections**: Show "(none)" for empty status categories
|
||||
- **Filter applied**: Only show matching section, still show total counts
|
||||
@@ -1,90 +0,0 @@
|
||||
---
|
||||
description: Reject an RFC with documented reason, marking it as declined
|
||||
agent: planner
|
||||
---
|
||||
|
||||
# Reject RFC
|
||||
|
||||
## Skills Required
|
||||
|
||||
- skills/mcp-tools-reference.md
|
||||
- skills/rfc-workflow.md
|
||||
- skills/rfc-templates.md
|
||||
|
||||
## Purpose
|
||||
|
||||
Transition an RFC to Rejected status with a documented reason. Rejected RFCs remain in the wiki for historical reference but are marked as declined.
|
||||
|
||||
## Invocation
|
||||
|
||||
Run `/rfc-reject <number>` where number is the RFC number:
|
||||
- `/rfc-reject 0006`
|
||||
- `/rfc-reject 6` (leading zeros optional)
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Validate RFC Number**
|
||||
- Normalize input (add leading zeros if needed)
|
||||
- Fetch RFC page: `RFC-NNNN: *`
|
||||
|
||||
2. **Check Current Status**
|
||||
- Parse frontmatter to get current status
|
||||
- **STOP** if status is not "Draft" or "Review"
|
||||
- Error: "RFC-NNNN is in [status] status. Only Draft or Review RFCs can be rejected."
|
||||
|
||||
3. **Require Rejection Reason**
|
||||
- Prompt: "Please provide the rejection reason (required):"
|
||||
- **STOP** if no reason provided
|
||||
- Error: "Rejection reason is required to document why this RFC was declined."
|
||||
|
||||
4. **Update RFC Page**
|
||||
- Change status: [current] → Rejected
|
||||
- Update "Updated" date
|
||||
- Add/update Decision section:
|
||||
```markdown
|
||||
## Decision
|
||||
|
||||
**Decision:** Rejected
|
||||
**Date:** YYYY-MM-DD
|
||||
**Decided By:** @[current user or maintainer]
|
||||
|
||||
**Reason:**
|
||||
|
||||
[User-provided rejection reason]
|
||||
```
|
||||
|
||||
5. **Update RFC-Index**
|
||||
- Remove entry from current section ("## Draft" or "## In Review")
|
||||
- Add entry to "## Rejected" section with reason summary
|
||||
|
||||
6. **Confirm Rejection**
|
||||
- Display updated status
|
||||
- Note that RFC remains in wiki for reference
|
||||
|
||||
## Visual Output
|
||||
|
||||
```
|
||||
+----------------------------------------------------------------------+
|
||||
| PROJMAN - RFC Rejection |
|
||||
+----------------------------------------------------------------------+
|
||||
|
||||
RFC-0006: Proposed Feature has been rejected.
|
||||
|
||||
Status: Review → Rejected
|
||||
Reason: Out of scope for current project direction
|
||||
|
||||
The RFC remains in the wiki for historical reference.
|
||||
If circumstances change, a new RFC can be created.
|
||||
```
|
||||
|
||||
## Validation Errors
|
||||
|
||||
- **RFC not found**: "RFC-NNNN not found. Check the number with /rfc-list"
|
||||
- **Wrong status**: "RFC-NNNN is [status]. Only Draft or Review RFCs can be rejected."
|
||||
- **No reason provided**: "Rejection reason is required. Please document why this RFC is being declined."
|
||||
|
||||
## Notes
|
||||
|
||||
- Rejected is a terminal state
|
||||
- To reconsider, create a new RFC that references the rejected one
|
||||
- Rejection reasons help future contributors understand project direction
|
||||
@@ -1,81 +0,0 @@
|
||||
---
|
||||
description: Submit a Draft RFC for review, transitioning status to Review
|
||||
agent: planner
|
||||
---
|
||||
|
||||
# Submit RFC for Review
|
||||
|
||||
## Skills Required
|
||||
|
||||
- skills/mcp-tools-reference.md
|
||||
- skills/rfc-workflow.md
|
||||
- skills/rfc-templates.md
|
||||
|
||||
## Purpose
|
||||
|
||||
Transition an RFC from Draft to Review status, indicating it's ready for maintainer evaluation. Optionally assign a champion to shepherd the RFC through review.
|
||||
|
||||
## Invocation
|
||||
|
||||
Run `/rfc-review <number>` where number is the RFC number:
|
||||
- `/rfc-review 0001`
|
||||
- `/rfc-review 1` (leading zeros optional)
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Validate RFC Number**
|
||||
- Normalize input (add leading zeros if needed)
|
||||
- Fetch RFC page: `RFC-NNNN: *`
|
||||
|
||||
2. **Check Current Status**
|
||||
- Parse frontmatter to get current status
|
||||
- **STOP** if status is not "Draft"
|
||||
- Error: "RFC-NNNN is in [status] status. Only Draft RFCs can be submitted for review."
|
||||
|
||||
3. **Validate Minimum Content**
|
||||
- Check for Summary section (required)
|
||||
- Check for Motivation section (required)
|
||||
- Check for Detailed Design > Overview (required)
|
||||
- Warn if Alternatives Considered is empty
|
||||
|
||||
4. **Optional: Assign Champion**
|
||||
- Ask: "Would you like to assign a champion? (Enter username or skip)"
|
||||
- Champion is responsible for driving the RFC through review
|
||||
|
||||
5. **Update RFC Page**
|
||||
- Change status: Draft → Review
|
||||
- Update "Updated" date
|
||||
- Set Champion if provided
|
||||
- Add Review Notes section if not present
|
||||
|
||||
6. **Update RFC-Index**
|
||||
- Remove entry from "## Draft" section
|
||||
- Add entry to "## In Review" section
|
||||
|
||||
7. **Confirm Transition**
|
||||
- Display updated status
|
||||
- Note next steps (review discussion, then /rfc-approve or /rfc-reject)
|
||||
|
||||
## Visual Output
|
||||
|
||||
```
|
||||
+----------------------------------------------------------------------+
|
||||
| PROJMAN - RFC Review Submission |
|
||||
+----------------------------------------------------------------------+
|
||||
|
||||
RFC-0005: Feature Idea submitted for review
|
||||
|
||||
Status: Draft → Review
|
||||
Champion: @assigned_user (or: unassigned)
|
||||
Updated: RFC-Index
|
||||
|
||||
Next steps:
|
||||
- Discuss in RFC wiki page comments or meetings
|
||||
- When decision reached: /rfc-approve 0005 or /rfc-reject 0005
|
||||
```
|
||||
|
||||
## Validation Errors
|
||||
|
||||
- **RFC not found**: "RFC-NNNN not found. Check the number with /rfc-list"
|
||||
- **Wrong status**: "RFC-NNNN is [status]. Only Draft RFCs can be reviewed."
|
||||
- **Missing sections**: "RFC-NNNN is missing required sections: [list]. Please complete before review."
|
||||
144
plugins/projman/commands/rfc.md
Normal file
144
plugins/projman/commands/rfc.md
Normal file
@@ -0,0 +1,144 @@
|
||||
---
|
||||
description: RFC lifecycle management - create, list, review, approve, reject
|
||||
agent: 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.
|
||||
|
||||
## Invocation
|
||||
|
||||
```
|
||||
/rfc <sub-command> [arguments]
|
||||
```
|
||||
|
||||
### Sub-Commands
|
||||
|
||||
| Sub-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 |
|
||||
|
||||
---
|
||||
|
||||
## 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 `/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 /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
|
||||
@@ -26,6 +26,7 @@ Unified setup command for all configuration needs.
|
||||
/setup --full # Full wizard (MCP + system + project)
|
||||
/setup --quick # Project-only setup
|
||||
/setup --sync # Update after repo move
|
||||
/setup --clear-cache # Clear plugin cache (between sessions only)
|
||||
```
|
||||
|
||||
## Mode Detection
|
||||
@@ -79,6 +80,21 @@ Steps:
|
||||
6. Update `.env`
|
||||
7. Confirm
|
||||
|
||||
## Mode: Clear Cache (--clear-cache)
|
||||
|
||||
Clear plugin cache to force fresh configuration reload.
|
||||
|
||||
**WARNING:** Only run between sessions, never mid-session. Clearing cache mid-session destroys MCP tool venv paths and breaks all MCP operations.
|
||||
|
||||
Steps:
|
||||
1. Execute: `rm -rf ~/.claude/plugins/cache/leo-claude-mktplace/`
|
||||
2. Inform user: "Cache cleared. Restart Claude Code for changes to take effect."
|
||||
|
||||
When to use:
|
||||
- After updating the marketplace (`git pull` or reinstall)
|
||||
- When MCP servers show stale configuration
|
||||
- When plugin changes don't take effect
|
||||
|
||||
## Visual Output
|
||||
|
||||
```
|
||||
|
||||
@@ -11,7 +11,7 @@ Provides templates for RFC wiki pages and defines the required/optional sections
|
||||
|
||||
## When to Use
|
||||
|
||||
- **Commands**: `/rfc-create` when generating new RFC pages
|
||||
- **Commands**: `/rfc create` when generating new RFC pages
|
||||
- **Integration**: Referenced by `rfc-workflow.md` for page structure
|
||||
|
||||
---
|
||||
|
||||
@@ -12,7 +12,7 @@ Defines the Request for Comments (RFC) system for capturing, reviewing, and trac
|
||||
## When to Use
|
||||
|
||||
- **Planner agent**: When detecting approved RFCs for sprint planning
|
||||
- **Commands**: `/rfc-create`, `/rfc-list`, `/rfc-review`, `/rfc-approve`, `/rfc-reject`
|
||||
- **Commands**: `/rfc create`, `/rfc list`, `/rfc review`, `/rfc approve`, `/rfc reject`
|
||||
- **Integration**: With `/sprint-plan` to select approved RFCs for implementation
|
||||
|
||||
---
|
||||
@@ -298,11 +298,11 @@ When RFC status changes:
|
||||
|
||||
| Component | How It Uses RFC System |
|
||||
|-----------|------------------------|
|
||||
| `/rfc-create` | Creates RFC page + updates RFC-Index |
|
||||
| `/rfc-list` | Reads and displays RFC-Index |
|
||||
| `/rfc-review` | Transitions Draft → Review |
|
||||
| `/rfc-approve` | Transitions Review → Approved |
|
||||
| `/rfc-reject` | Transitions Review/Draft → Rejected |
|
||||
| `/rfc create` | Creates RFC page + updates RFC-Index |
|
||||
| `/rfc list` | Reads and displays RFC-Index |
|
||||
| `/rfc review` | Transitions Draft -> Review |
|
||||
| `/rfc approve` | Transitions Review -> Approved |
|
||||
| `/rfc reject` | Transitions Review/Draft -> Rejected |
|
||||
| `/sprint-plan` | Detects Approved RFCs, transitions to Implementing |
|
||||
| `/sprint-close` | Transitions Implementing → Implemented |
|
||||
| `clarity-assist` | Suggests `/rfc-create` for feature ideas |
|
||||
| `/sprint-close` | Transitions Implementing -> Implemented |
|
||||
| `clarity-assist` | Suggests `/rfc create` for feature ideas |
|
||||
|
||||
Reference in New Issue
Block a user