Unique-AG/ai / .claude/skills/clarify-task
clarify-task
VerifiedAsk clarifying questions before implementing to ensure Python requirements are understood. Use when a task lacks detail, dependencies are unclear, or multiple interpretations are possible.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.4 KB |
SKILL.md
View on GitHub---
name: clarify-task
description: Ask clarifying questions before implementing to ensure Python requirements are understood. Use when a task lacks detail, dependencies are unclear, or multiple interpretations are possible.
license: MIT
compatibility: claude cursor opencode
metadata:
version: "1.0.0"
languages: all
audience: developers
workflow: planning
since: "2026-02-25"
---
# Clarify Task
Before implementing any Python work, pause and gather context so the solution matches what’s really needed.
## Steps
1. **Ask focused questions**
- Data flow, inputs/outputs, and architecture (async vs sync, service vs script)
- API contracts, dependencies, and integrations
- Authentication, authorization, and configuration expectations
- Edge cases, error handling, and rollback requirements
- UX/CLI expectations if applicable (prompts, flags, logging)
2. **Restate the requirements**
- Summarize your understanding in plain language
- Confirm the desired behavior, inputs, and success criteria
3. **Confirm before moving forward**
- Once you have enough context, ask if you can proceed with planning or implementation
- If questions remain, repeat steps 1–2 until confident
## Tools
- Use the `AskQuestion` tool to present multiple-choice clarifications when the extra structure helps.
- Keep responses brief and focused; avoid assumptions about unrelated components.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |