iikit-02-clarify

A tool for generating and validating ideas and other cognitive artifacts.

1|1|Updated Feb 12, 2026

Search Tags:#specification #requirements #product management #clarification #ambiguity #feature definition

Ready to run

npx skills add https://github.com/asm0dey/relay --skill iikit-02-clarify-asm0dey

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: iikit-02-clarify
Source: https://github.com/asm0dey/relay/tree/main/.tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-02-clarify
Command: npx skills add https://github.com/asm0dey/relay --skill iikit-02-clarify-asm0dey

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses underspecified areas in feature specifications by identifying ambiguities and generating targeted clarification questions to ensure clarity and completeness before planning.

Core Features & Use Cases

Ambiguity Detection: Scans feature specifications for missing information across various categories like functional scope, data models, and non-functional requirements.
Targeted Question Generation: Creates up to 5 concise, actionable questions with multiple-choice or short-answer formats.
Interactive Clarification: Guides users through answering questions sequentially, integrating answers directly into the spec.
Use Case: A product manager is defining a new feature. Before moving to the planning phase, they use this Skill to ensure all critical aspects of the feature are clearly defined, preventing potential rework later.

Quick Start

Use the iikit-02-clarify skill to identify and resolve ambiguities in the current feature specification.

Frequently Asked Questions about iikit-02-clarify

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

FAQPage Schema

How do I identify ambiguities in feature specifications?▼

Identify ambiguities in feature specifications by scanning documents against a defined taxonomy to find missing information across functional scope, data models, and non-functional requirements. This structured scanning process highlights underspecified areas needing further clarification before planning.

What are targeted clarification questions for product management?▼

Targeted clarification questions for product management are concise, actionable inquiries generated to resolve specification ambiguities. Up to five questions with multiple-choice or short-answer formats are created to guide users through refining scope, data models, and quality attributes interactively.

How do I resolve missing information in a feature definition?▼

Resolve missing information in a feature definition through interactive clarification. Answer targeted questions sequentially, and the answers are integrated directly into the specification document to ensure clarity and completeness before moving to the planning phase.

When do I need to clarify requirements for a feature specification?▼

You need to clarify requirements for a feature specification before moving to the planning phase. Clarifying requirements at this stage prevents potential rework later by ensuring all critical aspects of the feature, including non-functional requirements, are clearly defined.

Does ambiguity detection work for non-functional requirements?▼

Ambiguity detection works for non-functional requirements by scanning feature specifications for missing information across various categories. The taxonomy specifically includes quality attributes and non-functional requirements to ensure these critical areas are validated and refined.