clarify-spec

Resolves spec clarification markers and maintains spec alignment through structured question sessions.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/pandejesal/drone-nav-sar --skill clarify-spec-pandejesal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify-spec
Source: https://github.com/pandejesal/drone-nav-sar/tree/main/.swarm/bundled-skills/clarify-spec
Command: npx skills add https://github.com/pandejesal/drone-nav-sar --skill clarify-spec-pandejesal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Software specifications often contain vague language, unresolved [NEEDS CLARIFICATION] markers, and conflicting requirements that block planning and implementation. This Skill provides a structured protocol for resolving those ambiguities one question at a time while keeping the spec source consistent. ## Core Features & Use Cases - Marker Resolution: Scans the effective spec for [NEEDS CLARIFICATION] markers and implicit ambiguities such as vague adjectives, conflicting requirements, and untestable acceptance criteria. - Source-Aware Write-Back: Writes accepted answers to the resolved effective source (native .swarm/spec.md, OpenSpec, or Spec-Kit) without shadowing non-native specs. - Critic-Guarded Questioning: Consults a critic sounding board before surfacing each question, with overconfidence guards and always-surface protection for high-risk categories like security and breaking changes. - Use Case: After running /swarm specify, your spec contains six open markers. Invoke this Skill to walk through each ambiguity with multiple-choice options, then receive a clarification summary and a recommendation to proceed to planning. ## Quick Start Ask the assistant to clarify the open markers in the current effective spec by saying "clarify my spec" or invoking /swarm clarify.

Frequently Asked Questions about clarify-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve [NEEDS CLARIFICATION] markers in a spec?

Invoke the clarify-spec protocol after /swarm sdd status confirms a single resolved effective spec. It scans for markers and vague language, then asks questions one at a time with multiple-choice options, writing each accepted answer back to the spec source.

What happens when no effective spec exists for clarification?

The protocol does not activate when /swarm sdd status returns null, which occurs with no sources, competing sources like openspec/ and .specify/, or unselected features. You must disambiguate with /swarm sdd project or run /swarm specify first.

Does clarify-spec work with OpenSpec or Spec-Kit repositories?

Yes, it supports native .swarm/spec.md, OpenSpec, and Spec-Kit sources through source-aware write-back. For non-native sources it edits in place where possible or asks before materializing a native spec, never silently shadowing the original source.

How many clarification questions are asked per session?

A maximum of eight questions per session, presented one at a time with two to four multiple-choice options plus free-form input. When the limit is reached, the protocol reports remaining ambiguities and stops.

When should I use clarify-spec instead of the full clarify funnel?

Use clarify-spec when a spec already exists with surfaced markers needing resolution. The full four-stage funnel (inventory, classify, consult critic, surface) applies to open-ended uncertainty discovery in MODE: CLARIFY and MODE: PLAN, not marker resolution.