// Use when working in this Spec Kit repository and the user wants to resolve ambiguity in the active feature spec by asking targeted clarification questions and writing the accepted answers back into spec.md.
Use when adding or editing Zig code in ZINC and you want it to remain compatible with the auto-generated Zig API docs. Covers the comment format, supported tags, parser limitations, section naming, and validation steps needed for reliable HTML, JSON, text, and llms exports.
Use when working in this Spec Kit repository and the user wants a read-only consistency and coverage analysis across the active feature's spec.md, plan.md, and tasks.md before implementation.
Use when working in this Spec Kit repository and the user wants a requirements-quality checklist for the active feature, generated from the current spec, plan, and tasks artifacts.
Use when working in this Spec Kit repository and the user wants to create or amend the project constitution in .specify/memory/constitution.md and keep dependent templates aligned.
Use when working in this Spec Kit repository and the user wants to execute the active tasks.md plan, respecting checklist gates, task dependencies, and phase-by-phase implementation.
Use when working in this Spec Kit repository and the user wants to turn the active feature spec into an implementation plan and design artifacts such as research.md, data-model.md, contracts, and quickstart.md.
| name | speckit-clarify |
| description | Use when working in this Spec Kit repository and the user wants to resolve ambiguity in the active feature spec by asking targeted clarification questions and writing the accepted answers back into spec.md. |
Use this skill for the Spec Kit clarify phase.
../../../.claude/commands/speckit.clarify.md and treat it as the authoritative workflow.$ARGUMENTS referenced there.speckit-specify, speckit-clarify, speckit-plan, speckit-tasks, speckit-analyze, speckit-implement, speckit-checklist, speckit-constitution, and speckit-taskstoissues..specify/scripts/bash/*.sh and .specify/templates/*.md files the workflow calls for.