clarify-spec

Resolves specification clarification markers through structured one-at-a-time user questions.

Updated May 31, 2026
One-click install
npx skills add https://github.com/AlexanderNarbaev/agi --skill clarify-spec-alexandernarbaev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify-spec
Source: https://github.com/AlexanderNarbaev/agi/tree/main/.opencode/skills/clarify-spec
Command: npx skills add https://github.com/AlexanderNarbaev/agi --skill clarify-spec-alexandernarbaev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Specifications often contain ambiguous requirements, vague adjectives, and unresolved [NEEDS CLARIFICATION] markers that block planning and implementation. This Skill provides a disciplined protocol for resolving those ambiguities while keeping the spec and downstream planning aligned. ## Core Features & Use Cases - Marker Resolution: Scans .swarm/spec.md for [NEEDS CLARIFICATION] markers and implicit ambiguities such as vague adjectives, conflicting requirements, and untestable acceptance criteria. - Structured Questioning: Presents questions one at a time (max 8 per session) with 2-4 multiple-choice options, a recommended choice with reasoning, and free-form input support. - Critic Safeguards: Consults a critic sounding board before surfacing each question, applies an overconfidence guard against unsupported self-resolution, and enforces always-surface protection for scope, security, and breaking-change categories. - Delta-Based Updates: Writes accepted answers back to spec.md immediately using ADDED/MODIFIED/REMOVED requirement sections with strict FR-ID increment rules. - Use Case: After generating a spec with open markers, run the clarify flow to resolve each ambiguity interactively, then receive a Clarification Summary recommending whether to proceed to PLAN. ## Quick Start Ask the agent to clarify the open markers in .swarm/spec.md and answer each question as it is presented.

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 file?

Invoke the clarify flow on the existing .swarm/spec.md file. The protocol scans for markers and implicit ambiguities, then asks questions one at a time with multiple-choice options, writing each accepted answer back to the spec immediately.

How to clarify ambiguous requirements before planning?

Run the CLARIFY-SPEC mode after spec generation and before PLAN mode. It detects vague adjectives, conflicting requirements, and untestable acceptance criteria, then resolves them through up to 8 structured questions per session.

Can clarify-spec create a new specification file?

No. CLARIFY-SPEC never creates a spec. If .swarm/spec.md does not exist, it instructs you to run the specify command first and stops, since it only refines existing specifications.

What happens when the question limit is reached during clarification?

The session stops after 8 questions and reports a Clarification Summary listing questions asked, requirements added/modified/removed, and remaining open ambiguities, with a suggested next step such as continuing or moving to PLAN.

Why are some clarification questions never auto-resolved?

Always-surface categories like scope boundaries, security, breaking API changes, and deprecations must be asked to the user. The critic cannot drop or self-resolve these items, and unsupported default answers are reclassified as user decisions.