From agent-flow
This skill should be used when the user provides a vague request, asks to clarify requirements, structure a task, or refine a prompt for multi-agent orchestration.
npx claudepluginhub josix/agent-flow --plugin agent-flowThis skill uses the workspace's default tool permissions.
Prompt refinement transforms ambiguous or incomplete user requests into clear, structured task specifications suitable for multi-agent orchestration. This skill bridges natural language input and the precise specifications required by downstream agents.
Clarifies vague user requests via iterative Q&A loop and parallel subagent codebase exploration. Outputs scoped context brief for precise planning. Triggers on 'I want to...' or ambiguous scopes.
Decomposes ambiguous user requests via structured brainstorming and hypothesis-driven questions to detect underspecification, false premises, and multiple interpretations. For unclear coding tasks.
Enriches vague prompts via research on conversation history, codebase (grep/glob/git), docs, and web, then generates 1-6 grounded multiple-choice clarifying questions.
Share bugs, ideas, or general feedback.
Prompt refinement transforms ambiguous or incomplete user requests into clear, structured task specifications suitable for multi-agent orchestration. This skill bridges natural language input and the precise specifications required by downstream agents.
Ensure tasks entering the orchestration pipeline have:
Apply prompt refinement when:
/orchestrate or /plan commands**Goal**: <one-sentence objective stating what will be accomplished>
**Description**: <2-3 sentences providing context, constraints, and scope>
**Actions**:
1. <specific, atomic action with clear target>
2. <specific, atomic action with clear target>
3. ...
| Field | Requirements | Example |
|---|---|---|
| Goal | Single sentence, verb-first, specific outcome | "Implement rate limiting on /api/users endpoint" |
| Description | Context, scope boundaries, constraints | "Add rate limiting to prevent API abuse. Limit to 100 req/min per IP." |
| Actions | Numbered, ordered, atomic steps | "1. Explore existing middleware patterns" |
A prompt likely needs clarification if:
| Signal | Example | Issue |
|---|---|---|
| Missing scope | "fix the bug" | Which bug? Where? |
| Vague outcome | "make it better" | Better how? |
| Multiple meanings | "update the API" | Which endpoint? What change? |
| Implicit assumptions | "deploy it" | Where? How? |
For detailed ambiguity detection, see references/ambiguity-detection.md.
Before I proceed, I need to clarify:
<single focused question>
Options:
A) <most likely option>
B) <second most likely>
C) <third option if applicable>
D) Something else (please specify)
| Rule | Rationale |
|---|---|
| Single question | Reduces cognitive load |
| Concrete options | Speeds up response |
| Max two rounds | Avoids frustration |
| Include escape hatch | Prevents forced incorrect choice |
Always Clarify:
Safe to Assume:
For detailed clarification strategies, see references/clarification-strategies.md.
| Category | Example |
|---|---|
| Multi-file changes | "Add authentication to all routes" |
| Feature implementations | "Implement dark mode" |
| Bug investigation | "Fix the login issue" |
| Refactoring | "Refactor user service" |
| Integration | "Integrate Stripe" |
| Category | Example |
|---|---|
| Questions | "What does this function do?" |
| Single-file edits | "Add comment to line 42" |
| Git operations | "Commit these changes" |
| Documentation lookups | "Show API endpoints" |
Is it a question about existing code? -> Pass through
Does it require code changes? -> If no, pass through
Is target explicit AND single file? -> Pass through
Otherwise -> Refine for orchestration
For detailed orchestration detection, see references/orchestration-detection.md.
Is it orchestration-related?
├── NO -> Pass through unchanged
└── YES -> Continue to Step 2
Check ambiguity signals
├── High ambiguity -> Go to Step 3 (Clarify)
└── Low ambiguity -> Go to Step 4 (Refine)
| Score | Action |
|---|---|
| 0-2 | Proceed with refinement |
| 3-4 | State assumption and proceed |
| 5+ | Ask clarifying question |
| Prompt Type | Action |
|---|---|
| Clear + orchestration | Refine to template |
| Ambiguous + orchestration | Clarify then refine |
| Clear + non-orchestration | Pass through |
| Ambiguous + non-orchestration | Minimal clarification |