skills.rest
eavichay
eavichayCOMMUNITY
Explore all skills by this author →
GitHub

spec-clarify

Identifies ambiguities in feature specs via structured taxonomy-based scanning and interactive questioning loops.

Updated Jul 7, 2026
Search Tags:#documentation#specification#requirements#clarification#ambiguity#software-engineering
One-click install
npx skills add https://github.com/eavichay/mycli --skill spec-clarify-eavichay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-clarify
Source: https://github.com/eavichay/mycli/tree/main/.cursor/skills/spec-clarify
Command: npx skills add https://github.com/eavichay/mycli --skill spec-clarify-eavichay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves hidden ambiguities and missing decision points in technical specifications, preventing costly downstream rework and ensuring alignment before development begins.

Core Features & Use Cases

  • Ambiguity Scanning: Automatically audits feature specs against a comprehensive taxonomy of functional, technical, and non-functional requirements.
  • Interactive Clarification: Guides the user through a prioritized, sequential questioning loop to resolve critical gaps.
  • Automated Integration: Directly records confirmed answers into the specification file, maintaining a clean and updated source of truth.

Quick Start

Invoke the spec-clarify skill to audit the current feature specification and resolve any outstanding ambiguities.

Frequently Asked Questions about spec-clarify

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

FAQPage Schema
How do I eliminate ambiguity in a software feature specification?▼

To eliminate ambiguity in a feature specification, execute a taxonomy-based scan against your spec to identify missing decision points, then resolve them through an interactive questioning loop that records answers directly into the markdown spec file.

What is the best way to identify missing decision points in technical requirements?▼

The best way to identify missing decision points in technical requirements is to perform an automated ambiguity scan against a comprehensive taxonomy of non-functional and functional requirements before development begins.

How do I record specification clarifications directly into a markdown spec file?▼

You can record specification clarifications directly into a markdown spec file by using an interactive tool that appends confirmed answers from a guided questioning loop into your existing source of truth.

Does the spec clarification process require git and a specific directory structure?▼

Yes, the spec clarification process requires git for repository root detection and operates strictly within the .specify/ directory structure to validate mission briefs and adhere to spec-kit architectural standards.

When should I run an ambiguity scan on my feature specs?▼

You should run an ambiguity scan on your feature specs before development begins, ensuring alignment and preventing costly downstream rework caused by hidden ambiguities in your mission briefs.

Related Skills

Explore More Software Engineering Skills→
hachejhachej
45

setup-matt-pocock-skills

Configure repository issue tracking, triage labels, and domain documentation layouts.

Community
Intermediate
mathiasbourgoinmathiasbourgoin
2

roster-intake

Convert raw task inputs into validated briefs for Roster pipeline workflows.

Community
Advanced
EzekTec-IncEzekTec-Inc

speckit-git-commit

Automate Git commits after Spec Kit workflow lifecycle events.

Community
Intermediate
hashi-demo-labhashi-demo-lab

tf-domain-category

Identify ambiguity in Terraform specifications using an 8-category taxonomy.

Official
Advanced