lmiranda
e5ca804692
- Rename marketplace to lm-claude-plugins - Move MCP servers to root with symlinks - Add 6 PR tools to Gitea MCP (list_pull_requests, get_pull_request, get_pr_diff, get_pr_comments, create_pr_review, add_pr_comment) - Add clarity-assist plugin (prompt optimization with ND accommodations) - Add git-flow plugin (workflow automation) - Add pr-review plugin (multi-agent review with confidence scoring) - Centralize configuration docs - Update all documentation for v3.0.0 BREAKING CHANGE: MCP server paths changed, marketplace renamed Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
3.4 KiB
3.4 KiB
/clarify - Full Prompt Optimization
Purpose
Transform vague, incomplete, or ambiguous requests into clear, actionable specifications using the 4-D methodology with neurodivergent-friendly accommodations.
When to Use
- Complex multi-step requests
- Requirements with multiple possible interpretations
- Tasks requiring significant context gathering
- When user seems uncertain about what they want
4-D Methodology
Phase 1: Deconstruct
Break down the user's request into components:
- Extract explicit requirements - What was directly stated
- Identify implicit assumptions - What seems assumed but not stated
- Note ambiguities - Points that could go multiple ways
- List dependencies - External factors that might affect implementation
Phase 2: Diagnose
Analyze gaps and potential issues:
- Missing information - What do we need to know?
- Conflicting requirements - Do any stated goals contradict?
- Scope boundaries - What's in/out of scope?
- Technical constraints - Platform, language, architecture limits
Phase 3: Develop
Gather clarifications through structured questioning:
ND-Friendly Question Rules:
- Present 2-4 concrete options (never open-ended alone)
- Include "Other" for custom responses
- Ask 1-2 questions at a time maximum
- Provide brief context for why you're asking
- Check for conflicts with previous answers
Example Format:
To help me understand the scope better:
**How should errors be handled?**
1. Silent logging (user sees nothing)
2. Toast notifications (brief, dismissible)
3. Modal dialogs (requires user action)
4. Other
[Context: This affects both UX and how much error-handling code we need]
Phase 4: Deliver
Produce the refined specification:
## Clarified Request
### Summary
[1-2 sentence description of what will be built]
### Scope
**In Scope:**
- [Item 1]
- [Item 2]
**Out of Scope:**
- [Item 1]
### Requirements
| # | Requirement | Priority | Notes |
|---|-------------|----------|-------|
| 1 | ... | Must | ... |
| 2 | ... | Should | ... |
### Assumptions
- [Assumption made based on conversation]
### Open Questions
- [Any remaining ambiguities, if any]
Conflict Detection
Before each question, review previous answers for conflicts:
[Internal check]
Previous: User said "keep it simple"
Current question about: Adding configuration options
Potential conflict: More options = more complexity
→ Acknowledge: "Earlier you mentioned keeping it simple. With that in mind..."
Escalation Protocol
If the request is particularly messy or the user seems overwhelmed:
- Acknowledge the complexity
- Offer to start with just ONE aspect
- Build incrementally
"This touches a lot of areas. Rather than tackle everything at once,
let's start with [most critical piece]. Once that's clear, we can
add the other parts. Sound good?"
Example Interaction
User: Make the app faster
Clarify Response:
Let me help clarify what kind of performance improvements you're looking for.
**What type of slowness are you experiencing?**
1. Initial page load takes too long
2. Interactions feel sluggish (clicking, typing)
3. API calls are slow
4. All of the above
5. Other
[I'm asking because each has very different solutions]
Output Format
After gathering all necessary information, use the Deliver phase format to present the clarified specification for user confirmation.