feat(commands): make dispatch files active command handlers

All 25 dispatch files now have name: in frontmatter with Workflow
section that displays sub-commands and prompts for selection.
Bare /noun invocation is now useful instead of a dead end.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-02-08 19:12:12 -05:00
parent bbce9ed321
commit 271e0210a5
25 changed files with 324 additions and 89 deletions

View File

@@ -1,13 +1,18 @@
---
description: Architecture Decision Records management
name: adr
description: Architecture Decision Records management — type /adr <action> for commands
---
# /adr
## Sub-commands
Architecture Decision Records management for projman.
| Sub-command | Description |
|-------------|-------------|
When invoked without a sub-command, display available actions and ask which to run.
## Available Commands
| Command | Description |
|---------|-------------|
| `/adr create` | Create a new ADR wiki page |
| `/adr list` | List all ADRs by status |
| `/adr update` | Update an existing ADR |
@@ -21,3 +26,9 @@ description: Architecture Decision Records management
/adr update <ADR-NNNN> [--status accepted|deprecated]
/adr supersede <ADR-NNNN> --by <ADR-MMMM>
```
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,13 +1,22 @@
---
description: Label management
name: labels
description: Label management — type /labels <action> for commands
---
# /labels
Label management for projman.
## Sub-commands
When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description |
|-------------|-------------|
## Available Commands
| Command | Description |
|---------|-------------|
| `/labels sync` | Sync label taxonomy to Gitea repository |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,13 +1,18 @@
---
description: Project lifecycle management — concept to MVP
name: project
description: Project lifecycle management — type /project <action> for commands
---
# /project
## Sub-commands
Project lifecycle management from concept to MVP.
| Sub-command | Description |
|-------------|-------------|
When invoked without a sub-command, display available actions and ask which to run.
## Available Commands
| Command | Description |
|---------|-------------|
| `/project initiation` | Analyze source, create charter, decompose into epics |
| `/project plan` | Create WBS, risk register, sprint roadmap |
| `/project status` | Full project hierarchy view |
@@ -21,3 +26,9 @@ description: Project lifecycle management — concept to MVP
/project status <project-name>
/project close <project-name>
```
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,13 +1,22 @@
---
description: projman plugin management
name: projman
description: projman plugin management — type /projman <action> for commands
---
# /projman
Plugin-level management commands for projman.
## Sub-commands
When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description |
|-------------|-------------|
## Available Commands
| Command | Description |
|---------|-------------|
| `/projman setup` | Configure projman for a project |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command

View File

@@ -1,4 +1,5 @@
---
name: rfc
description: RFC lifecycle management - create, list, review, approve, reject
agent: planner
---
@@ -15,22 +16,30 @@ agent: planner
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, display available actions and ask which to run.
## Invocation
```
/rfc <sub-command> [arguments]
```
### Sub-Commands
## Available Commands
| Sub-Command | Usage | Description |
|-------------|-------|-------------|
| 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 |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command
---
## Sub-Command: create

View File

@@ -1,18 +1,27 @@
---
description: Sprint lifecycle management
name: sprint
description: Sprint lifecycle management — type /sprint <action> for commands
---
# /sprint
Sprint lifecycle management for projman.
## Sub-commands
When invoked without a sub-command, display available actions and ask which to run.
| Sub-command | Description |
|-------------|-------------|
## Available Commands
| Command | Description |
|---------|-------------|
| `/sprint plan` | Analyze requirements, create issues, request approval |
| `/sprint start` | Begin execution, load context, dispatch tasks |
| `/sprint status` | Check progress, blockers, completion percentage |
| `/sprint close` | Capture lessons learned, close milestone |
| `/sprint review` | Pre-close code quality review |
| `/sprint test` | Run/generate tests for sprint scope |
## Workflow
1. Display the table above
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command