How does the skill handle my answers during the session?

It incrementally updates the relevant feature specifications in your .specify/memory/ directory, adding acceptance criteria and removing markers as you provide details.

Are there any prerequisites before running this skill?

Yes, this is Step 5 of the StackShift process. You should have already completed a Gap Analysis (Step 4) so that the specifications contain [NEEDS CLARIFICATION] markers to resolve.

Which command does this skill utilize?

This skill primarily leverages the /speckit.clarify command from the GitHub Spec Kit to manage a structured clarification workflow.

What is the primary purpose of the complete-spec skill?

It uses an interactive dialogue to resolve missing details or ambiguities in your project specifications, ensuring Claude has clear, testable instructions for the implementation phase.

Spec Clarification Toolkit

Name: Spec Clarification Toolkit
Author: jschulte

byjschulte

•

Productivity & Workflow

Resolves project ambiguities through interactive Q&A to finalize technical specifications and implementation plans.

About

This skill facilitates the transition from gap analysis to implementation by conducting a structured dialogue between Claude and the developer. By identifying '[NEEDS CLARIFICATION]' markers within project specification files, it uses the GitHub Spec Kit to ask targeted questions about UI/UX details, business logic, and priorities. The skill automatically updates the project's memory with your answers, ensuring that all subsequent coding tasks are based on complete, unambiguous requirements, which reduces rework and technical debt.

Key Features

Structured requirement gathering for UI/UX and business rules
Systematic removal of [NEEDS CLARIFICATION] markers
Interactive Q&A session to resolve specification gaps
1 GitHub stars
Automated updates to feature specs in .specify/memory/
Priority-based clarification grouping (P0-P3)

Use Cases

Finalizing requirements after reverse-engineering an existing codebase
Preparing technical documentation for automated implementation steps
Defining specific acceptance criteria for missing features in a greenfield app

About

Key Features

Structured requirement gathering for UI/UX and business rules
Systematic removal of [NEEDS CLARIFICATION] markers
Interactive Q&A session to resolve specification gaps
1 GitHub stars
Automated updates to feature specs in .specify/memory/
Priority-based clarification grouping (P0-P3)

Use Cases

Finalizing requirements after reverse-engineering an existing codebase
Preparing technical documentation for automated implementation steps
Defining specific acceptance criteria for missing features in a greenfield app