lmiranda
2d51df7a42
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
name
| name |
|---|
| clarity quick-clarify |
/clarity quick-clarify - Rapid Clarification Mode
Visual Output
+----------------------------------------------------------------------+
| CLARITY-ASSIST - Quick Clarify |
+----------------------------------------------------------------------+
Purpose
Single-pass clarification for requests that are mostly clear but need minor disambiguation.
When to Use
- Request is fairly clear, just one or two ambiguities
- User is in a hurry
- Follow-up to an already-clarified request
- Simple feature additions or bug fixes
Skills to Load
skills/nd-accommodations.md- ND-friendly question patternsskills/clarification-techniques.md- Echo and micro-summary techniquesskills/escalation-patterns.md- When to escalate to full/clarity clarify
Workflow
- Echo Understanding - Restate in a single sentence
- Quick Disambiguation - Ask ONE multiple-choice question if needed
- Proceed or Confirm - Start work or offer micro-summary
Output Format
No formal specification document needed. Proceed after brief confirmation, documenting assumptions inline with the work.
Escalation
If complexity emerges, offer to switch to full /clarity clarify:
"This is more involved than it first appeared. Want me to switch
to a more thorough clarification process?"