speckit-clarify

Interactively clarify ambiguous requirements in a spec.md before planning — generates targeted questions for the requester to resolve TBDs in the pickup-points-modal feature spec.

Jump to install

Repository: vtex/pickup-points-modal
Last source activity: May 14, 2026 at 19:22
Detected SKILL.md language: English
Stars: 5
Forks: 4

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/vtex/pickup-points-modal --skill speckit-clarify

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

name	speckit-clarify
description	Interactively clarify ambiguous requirements in a spec.md before planning — generates targeted questions for the requester to resolve TBDs in the pickup-points-modal feature spec.
type	skill

speckit-clarify

Generates focused questions to unblock a spec with TBDs or ambiguities. Runs between speckit-specify and speckit-plan.

When to use

spec.md has 2+ TBD markers in required fields.
Vague acceptance criteria ("it should just work well").
A stakeholder was not explicit about edge cases.

Flow

Read specs/<slug>/spec.md.
Identify gaps in:
- Business Context (who, why, metric)
- Architectural Decisions (alternatives, risks)
- Technical Contract (props, fixtures, i18n, acceptance)
Generate at most 5 questions per iteration, ordered by impact.
Wait for user replies.
Update spec.md with the answers — preserve history under a ## Clarifications section at the end of the file.

Good questions

Specific: "Should the modal close when a pickup is chosen? Before or after the confirm step?"
Actionable: the answer changes the plan.
Unique: not already answered earlier in the spec.

Bad questions

"Anything else?"
"What do you think?"
Questions the agent could answer by reading the code.

Back to search Back to installation

implementing

Implement an approved spec end-to-end in the pickup-points-modal repo — branch, code, tests, lint, typecheck, build, commit, and open a PR following Conventional Commits and the project constitution.

2026-05-14

specification

Generate an SDD (Spec Driven Development) document for a new feature in the pickup-points-modal, covering Business Context, Architectural Decisions, and Technical Contract before any code is written.

2026-05-14

speckit-analyze

Audit consistency between spec.md, plan.md, tasks.md, and the actual code in the pickup-points-modal — flagging drift, missing tasks, or out-of-spec changes before PR review.

2026-05-14

View all from this repository

name	speckit-clarify
description	Interactively clarify ambiguous requirements in a spec.md before planning — generates targeted questions for the requester to resolve TBDs in the pickup-points-modal feature spec.
type	skill

speckit-clarify

Generates focused questions to unblock a spec with TBDs or ambiguities. Runs between speckit-specify and speckit-plan.

When to use

spec.md has 2+ TBD markers in required fields.
Vague acceptance criteria ("it should just work well").
A stakeholder was not explicit about edge cases.

Flow

Read specs/<slug>/spec.md.
Identify gaps in:
- Business Context (who, why, metric)
- Architectural Decisions (alternatives, risks)
- Technical Contract (props, fixtures, i18n, acceptance)
Generate at most 5 questions per iteration, ordered by impact.
Wait for user replies.
Update spec.md with the answers — preserve history under a ## Clarifications section at the end of the file.

Good questions

Specific: "Should the modal close when a pickup is chosen? Before or after the confirm step?"
Actionable: the answer changes the plan.
Unique: not already answered earlier in the spec.

Bad questions

"Anything else?"
"What do you think?"
Questions the agent could answer by reading the code.

speckit-clarify

Source facts

Install options

Review the source files

speckit-clarify

When to use

Flow

Good questions

Bad questions

More from this repository

More from this repository

speckit-clarify

When to use

Flow

Good questions

Bad questions