analyst:clarify

Identify and resolve feature requirement ambiguities before design phase.

Updated Feb 24, 2026

Search Tags:#workflow #requirements #heuristics #clarification #ambiguity #design phase

Ready to run

npx skills add https://github.com/atournayre/claude-personas --skill analyst-clarify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyst:clarify
Source: https://github.com/atournayre/claude-personas/tree/main/analyst/skills/clarify
Command: npx skills add https://github.com/atournayre/claude-personas --skill analyst-clarify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the critical need to identify and resolve ambiguities in feature requirements before proceeding to the design phase, preventing costly rework and ensuring clarity.

Core Features & Use Cases

Ambiguity Identification: Systematically checks for underspecified areas across edge cases, error handling, integration points, backward compatibility, performance, and security.
Resolution Strategies: Offers both interactive (user questioning) and automatic (heuristic-based) methods for resolving identified ambiguities.
Decision Documentation: Records all decisions made, whether interactive or automatic, for future reference and auditability.
Use Case: Before designing a new user authentication flow, this Skill would prompt for details on password reset procedures, account lockout policies, and integration with existing SSO solutions.

Quick Start

Run the analyst clarify skill to identify and resolve ambiguities for the current feature.

Frequently Asked Questions about analyst:clarify

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

FAQPage Schema

How do I resolve ambiguities in feature requirements before starting the design phase?▼

Resolve ambiguities in feature requirements by systematically checking underspecified areas like edge cases, error handling, integration points, and security before the design phase. This Skill identifies gaps using interactive questioning or automatic heuristics to prevent costly rework.

What is the best way to identify missing edge cases and error handling paths in software requirements?▼

Identify missing edge cases and error handling paths through targeted interactive questioning or automatic heuristics. This process scans requirements for underspecified areas including backward compatibility, performance constraints, and security to ensure complete feature coverage.

Can I automatically resolve requirement ambiguities without manual user input?▼

You can automatically resolve requirement ambiguities using built-in heuristics as an alternative to interactive user questioning. Both methods systematically evaluate edge cases, integration points, and performance, documenting all decisions in a workflow state file for auditability.

How do I document requirement clarification decisions for future reference?▼

Document requirement clarification decisions automatically in a workflow state file. Whether ambiguities are resolved through interactive questioning or automatic heuristics, all choices regarding edge cases and security are recorded to ensure future reference and auditability.

When should I use a requirement clarification workflow in software engineering?▼

Use a requirement clarification workflow before designing complex features like user authentication flows. It helps define critical details such as password reset procedures, account lockout policies, and SSO integration by resolving ambiguities early.

What types of integration and compatibility issues should I check for before designing a feature?▼

Check for integration points, backward compatibility, performance constraints, and security vulnerabilities before designing a feature. A systematic ambiguity resolution process identifies these underspecified areas to ensure robust software engineering outcomes.