Clarify

Skill pooyagolchian/specforge/plugins/specforge/skills/clarify

Spec-driven AI development lifecycle for Claude Code — spec-kit + AI-DLC fused, with hook-enforced human-approval gates. Installable plugin + marketplace.

Install

npx -y skills add pooyagolchian/specforge --skill clarify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Resolve the open questions and [NEEDS CLARIFICATION] markers in a feature spec before planning. Use when a spec has unresolved unknowns, the user wants to answer clarifying questions, or asks to clarify requirements. Writes a reviewable questions file and folds answers back into spec.md.

SKILL.md

2.3 KB, as published. Nobody here has run it

/specforge:clarify — resolve unknowns before planning

Convert the spec's [NEEDS CLARIFICATION] markers into concrete decisions using a questions-in-a-file flow (from AI-DLC): more reviewable and diffable than chatting, and it keeps a record. Run this between /specforge:specify and /specforge:plan.

When to use

A spec still contains [NEEDS CLARIFICATION] markers or Open Questions.
The user wants to answer outstanding questions to firm up requirements.

Steps

Read the active feature's spec.md (the active feature is in specforge/state.md's  marker). Collect every [NEEDS CLARIFICATION] and Open Question.
Write specforge/specs/NNN-slug/clarifications.md listing each question with multiple-choice options A–E plus an [Answer]: line the human fills in. Example:
```
## Q1 — How should duplicate emails be handled on signup?
- A) Reject with 409
- B) Treat as login
- C) Merge accounts
- D) Allow duplicates
- E) Other / custom
[Answer]:
```
Tell the user they can answer inline (e.g. [Answer]: A), combine (B and C), or write a custom answer, then say "answers ready".
When the user returns with answers, re-read the file, apply each decision into spec.md (replace the corresponding [NEEDS CLARIFICATION] with the concrete requirement), and remove the resolved Open Questions. Keep unresolved ones flagged.
Update specforge/state.md: add/ensure | NNN-slug | clarify | done | <date> |.
Audit (append, with the human's raw answers — never summarized): | <today ISO-8601> | NNN-slug | clarify | Resolved Q1=A, Q2=B+C, … |.
Report remaining unknowns (if any) and suggest /specforge:approve specify then /specforge:plan.

Guardrails

Do not answer the questions yourself unless the user asks you to propose defaults. The point is to capture human decisions.
Fold answers into requirements as testable statements, preserving FR/NFR IDs.