116 lines
2.3 KiB
Markdown
116 lines
2.3 KiB
Markdown
|
---
|
||
|
|
status: legacy
|
||
|
|
note: "For maintenance of existing commands only. Prefer skills for new functionality."
|
||
|
|
model_tier:
|
||
|
|
gather: main
|
||
|
|
prioritize: main
|
||
|
|
apply: main
|
||
|
|
verify: main
|
||
|
|
---
|
||
|
|
|
||
|
|
# Workflow: Improve Command (LEGACY)
|
||
|
|
|
||
|
|
> **LEGACY WORKFLOW**: This workflow is for maintaining existing slash commands. For new functionality, prefer creating skills via `/cc-architect` (create-skill workflow) instead.
|
||
|
|
|
||
|
|
## When to use
|
||
|
|
|
||
|
|
- After using command and finding friction
|
||
|
|
- Description doesn't trigger correctly
|
||
|
|
- Clarify or simplify instructions
|
||
|
|
- Periodic maintenance
|
||
|
|
|
||
|
|
## Inputs required
|
||
|
|
|
||
|
|
- **command_path** - Path to command file
|
||
|
|
- **friction_notes** (optional) - Specific friction points
|
||
|
|
|
||
|
|
## Task document
|
||
|
|
|
||
|
|
Create: `.claude/plugin-data/slash-command-architect/tasks/improve-command-<command-name>-<date>.md`
|
||
|
|
|
||
|
|
## Output
|
||
|
|
|
||
|
|
- Task doc records changes
|
||
|
|
- Improved command verified and ready
|
||
|
|
- Optional follow-up audit offered
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Note on scope
|
||
|
|
|
||
|
|
Commands are simpler. Workflow is lightweight with fewer steps.
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Subtasks
|
||
|
|
|
||
|
|
### 1. Gather friction data
|
||
|
|
|
||
|
|
Subagent: Main.
|
||
|
|
|
||
|
|
**Do:**
|
||
|
|
- Check `.claude/plugin-data/slash-command-architect/tasks/` for mentions
|
||
|
|
- Ask user for pain points
|
||
|
|
- List in task doc
|
||
|
|
|
||
|
|
**Focus areas:**
|
||
|
|
- Description triggers (not invoking when expected, or unexpectedly)
|
||
|
|
- Instruction clarity (doing wrong thing)
|
||
|
|
- Tool permissions (missing tools or overly broad)
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
### 2. Prioritize improvements
|
||
|
|
|
||
|
|
Subagent: Main (inline judgment).
|
||
|
|
|
||
|
|
**Do:**
|
||
|
|
- Review friction notes
|
||
|
|
- Filter one-time issues
|
||
|
|
- Prioritize by impact
|
||
|
|
- Write to task doc
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
### 3. Apply improvements
|
||
|
|
|
||
|
|
Subagent: Main.
|
||
|
|
Read: `${CLAUDE_PLUGIN_ROOT}/references/layout/descriptions.md`
|
||
|
|
|
||
|
|
**Do per improvement:**
|
||
|
|
- Read command file
|
||
|
|
- Make targeted edit
|
||
|
|
- Document in task doc
|
||
|
|
|
||
|
|
**Common improvements:**
|
||
|
|
- Refine description for clearer triggers
|
||
|
|
- Simplify/clarify instructions
|
||
|
|
- Adjust tool permissions
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
### 4. Verify and reflect
|
||
|
|
|
||
|
|
Subagent: Main.
|
||
|
|
|
||
|
|
**Do:**
|
||
|
|
- Verify frontmatter valid YAML
|
||
|
|
- Check description follows "When/Why, Not How"
|
||
|
|
- Report summary
|
||
|
|
|
||
|
|
Offer: "Run quick audit on improved command?"
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
### 5. Record decisions (if applicable)
|
||
|
|
|
||
|
|
Subagent: Main.
|
||
|
|
|
||
|
|
**When to record:**
|
||
|
|
- Exceptions to description formula
|
||
|
|
- Tool permission changes
|
||
|
|
|
||
|
|
**How:**
|
||
|
|
- Template: `references/tool-patterns/templates/decision-record-template.md`
|
||
|
|
- Write: `<plugin_path>/.decisions/YYYY-MM-DD-<topic>.md`
|