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:
@@ -1,14 +1,23 @@
|
||||
---
|
||||
description: Prompt optimization and requirement clarification
|
||||
name: clarity
|
||||
description: Prompt optimization and requirement clarification — type /clarity <action> for commands
|
||||
---
|
||||
|
||||
# /clarity
|
||||
|
||||
Prompt optimization and requirement clarification with ND-friendly accommodations.
|
||||
|
||||
## Sub-commands
|
||||
When invoked without a sub-command, display available actions and ask which to run.
|
||||
|
||||
| Sub-command | Description |
|
||||
|-------------|-------------|
|
||||
## Available Commands
|
||||
|
||||
| Command | Description |
|
||||
|---------|-------------|
|
||||
| `/clarity clarify` | Full 4-D methodology for complex requests |
|
||||
| `/clarity quick-clarify` | Rapid mode for simple disambiguation |
|
||||
|
||||
## Workflow
|
||||
|
||||
1. Display the table above
|
||||
2. Ask: "Which command would you like to run?"
|
||||
3. Route to the selected sub-command
|
||||
|
||||
Reference in New Issue
Block a user