speckit-clarify

Identifies ambiguities in feature specs and integrates answers into the .specify directory using Markdown and PowerShell hooks.

1|Updated Jan 23, 2021
One-click install
npx skills add https://github.com/Dangerdan9631/Vayeate --skill speckit-clarify-dangerdan9631
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Dangerdan9631/Vayeate/tree/main/vayeate-theme-studio/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/Dangerdan9631/Vayeate --skill speckit-clarify-dangerdan9631

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires spec-kit, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify and resolve underspecified areas in feature specifications by asking targeted clarification questions and encoding answers back into the spec.

Core Features & Use Cases

  • Targeted Clarification: Asks up to 5 highly targeted clarification questions.
  • Spec Integration: Encodes answers back into the spec file.
  • Compatibility: Requires spec-kit project structure with a .specify/ directory.
  • Use Case: For a feature spec with potential ambiguities or missing decision points, use this Skill to detect and reduce them, directly improving the spec quality.

Quick Start

Run the clarifying command: /speckit-clarify

Frequently Asked Questions about speckit-clarify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve ambiguities in a feature specification?

To resolve ambiguities in a feature specification, this tool asks up to 5 targeted clarification questions and integrates the answers directly back into the spec file to improve overall quality.

What is the process for clarifying underspecified areas in a spec-kit project?

The clarification process identifies missing decision points in a spec-kit project, prompts the user for answers, and encodes those answers directly into the feature specification markdown file.

Do I need a specific directory structure to clarify feature specifications?

Yes, you need an existing spec-kit project structure with a .specify/ directory to use this clarification tool, as it relies on this environment to manipulate markdown specifications.

Can I automate checks before and after specification clarification?

Yes, this specification clarification tool supports hooks for pre and post clarification execution, allowing you to automate prerequisite checks using PowerShell before modifying the spec.

How many clarification questions will I be asked for my feature spec?

You will be asked up to 5 highly targeted clarification questions designed to detect and reduce ambiguities or missing decision points in your feature specification.

What is the best way to update a markdown spec with new decision points?

The best way to update a markdown spec is using this tool to detect underspecified areas, ask targeted questions, and encode the resolved answers directly into the feature specification file.