# Speckit Clarify

> Use when resolving Spec Kit open questions, NEEDS CLARIFICATION markers, or ambiguous feature requirements before planning.

- Skill: `me-cedric/speckit-clarify` (Agent Skill)
- Install (CLI): `npx skillmds@latest add me-cedric/speckit-clarify`
- Raw SKILL.md: https://api.skillmd.com/api/skills/me-cedric/speckit-clarify/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: me-cedric (https://skillmd.com/u/me-cedric)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/me-cedric/speckit-clarify

---


# Spec Kit Clarify

Read `AGENTS.md`, the target `spec.md`, and any checklist or product source the
spec references.

## Do

1. Find every `[NEEDS CLARIFICATION]` marker and ambiguous requirement.
2. Ask only questions that change scope, security/privacy, user experience, or
   acceptance criteria.
3. Use sensible defaults for low-impact gaps and document them as assumptions.
4. Update the spec with answers; do not hide unresolved blockers.

## Done

- No blocking ambiguity remains.
- Updated spec records decisions and assumptions.
- Planning can proceed or blockers are clearly listed.