refine-outcomes
The refine-outcomes skill clarifies user requests by distinguishing between desired outcomes and technical implementations. When users describe what they want, this tool identifies whether they've stated business or user-level outcomes or instead focused on what to build, then helps reframe implementation-focused requests into clear outcome statements. Use this skill during project planning or requirement gathering to ensure discussions focus on the value delivered rather than technical details.
git clone --depth 1 https://github.com/DheerG/swarms /tmp/refine-outcomes && cp -r /tmp/refine-outcomes/skills/refine-outcomes ~/.claude/skills/refine-outcomesSKILL.md
The user has described what they want. Check if they've stated outcomes or implementations. An outcome says what changes for the user or business. An implementation says what to build. If they wrote implementations, help them restate as outcomes. If they wrote outcomes, confirm them and move on. Keep outcomes short — one or two lines each, in plain language. Do not add technical detail, metrics, or architecture. Do not make outcomes longer or more formal than what the user wrote. Simplify, never elaborate.
Read-only swarm team member. Spawned by swarm via Agent tool with team_name. Tools restricted to read and research only — no Edit, Write, or NotebookEdit. Operational guidance comes from the briefing template at spawn time.
Launch a code-mode agent team
Scaffold a custom workflow — generates a mode skill and shortcut command
Launch a general-mode agent team
Interactively launch an agent team with guided setup
Walk through swarm's core concepts and launch your first team
Run recursive refinement on the current branch and PR
Launch a triage-mode agent team — diagnose an issue without changing it