Run any Skill in Manus with one click

speckit-clarify

Stars456

Forks19

UpdatedMarch 29, 2026 at 17:06

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.

Installation

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.

Run Skill in Manus

Source

zolotukhin

zolotukhin/zinc

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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.

Speckit Clarify

Use this skill for the Spec Kit clarify phase.

Read ../../../.claude/commands/speckit.clarify.md and treat it as the authoritative workflow.
Treat the current user request as the $ARGUMENTS referenced there.
Translate slash-command references to Codex skill names such as speckit-specify, speckit-clarify, speckit-plan, speckit-tasks, speckit-analyze, speckit-implement, speckit-checklist, speckit-constitution, and speckit-taskstoissues.
Use the repo-local .specify/scripts/bash/*.sh and .specify/templates/*.md files the workflow calls for.
Follow the source workflow's interaction model: ask one clarification question at a time, keep the total within the documented limit, and update the spec incrementally after each accepted answer.
Do not create Codex custom prompt files. Codex support in this repo is skill-based.

More from this repository

same repository

zig-docgen

zolotukhin/zinc

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.

2026-05-25456

speckit-analyze

zolotukhin/zinc

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.

2026-03-29456

speckit-checklist

zolotukhin/zinc

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.

2026-03-29456

speckit-constitution

zolotukhin/zinc

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.

2026-03-29456

speckit-implement

zolotukhin/zinc

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.

2026-03-29456

speckit-plan

zolotukhin/zinc

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.

2026-03-29456

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.

Speckit Clarify

Use this skill for the Spec Kit clarify phase.

Read ../../../.claude/commands/speckit.clarify.md and treat it as the authoritative workflow.
Treat the current user request as the $ARGUMENTS referenced there.
Translate slash-command references to Codex skill names such as speckit-specify, speckit-clarify, speckit-plan, speckit-tasks, speckit-analyze, speckit-implement, speckit-checklist, speckit-constitution, and speckit-taskstoissues.
Use the repo-local .specify/scripts/bash/*.sh and .specify/templates/*.md files the workflow calls for.
Follow the source workflow's interaction model: ask one clarification question at a time, keep the total within the documented limit, and update the spec incrementally after each accepted answer.
Do not create Codex custom prompt files. Codex support in this repo is skill-based.