cmd-speckit-clarify
/speckit.clarify
Agent skill wrapper for the Claude command /speckit.clarify.
When the original command text references {{INPUT}}, $1, or named arguments, map them from the user's current request.
Command Instructions
Systematically resolve underspecified areas in a feature spec through structured questioning. Run before /speckit.plan.
Steps
-
Locate the spec:
- If input names a feature or file path, use it.
- Otherwise check
.specify/specs/*/spec.md; if multiple, ask which to clarify. - Fall back to
spec.mdin the project root.
-
Load context: Read
spec.mdand.specify/memory/constitution.mdif present. -
Scan for ambiguities across nine taxonomy categories:
- Functional scope, Data model, UX flows, Non-functional attributes, Integration points, Edge cases, Constraints, Terminology, Completion signals.
-
Select questions: Choose the 5 highest-impact ambiguities. Prioritize by: scope > security > UX > technical detail. Each question must materially affect architecture, data modeling, testing, UX, or compliance.
-
Ask one question at a time:
- Present the question with 2-5 multiple-choice options (or note that a short phrase is acceptable).
- Mark the recommended answer with reasoning.
- Wait for the user's answer before asking the next question.
-
Update spec incrementally: After each answer, incorporate the clarification naturally into the relevant spec section. Do not append a Q&A log — merge it into the prose.
-
Final validation: Check for duplicates, contradictions, and terminology drift across the updated spec.
-
Report: Coverage map across all nine ambiguity categories (resolved / deferred / clear / outstanding).
Next step: Run /speckit.plan to generate the technical implementation plan.
{{INPUT}}
More from gsmlg-dev/code-agent
elixir-architect
Use when designing or architecting Elixir/Phoenix applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models with Ash Framework, structuring multi-app projects with path-based dependencies, or preparing handoff documentation for Director/Implementor AI collaboration
17flutter-animating-apps
Implements animated effects, transitions, and motion in a Flutter app. Use when adding visual feedback, shared element transitions, or physics-based animations.
17flutter-handling-concurrency
Executes long-running tasks in background isolates to keep the UI responsive. Use when performing heavy computations or parsing large datasets.
16flutter-caching-data
Implements caching strategies for Flutter apps to improve performance and offline support. Use when retaining app data locally to reduce network requests or speed up startup.
16flutter-embedding-native-views
Embeds native Android, iOS, or macOS views into a Flutter app. Use when integrating complex native components like maps or web views.
16flutter-setting-up-on-windows
Sets up a Windows environment for Flutter development. Use when configuring a Windows machine to run, build, or deploy Flutter applications for Windows desktop or Android.
16