Can the skill output in different languages?

Yes, it checks the 'language' field in your project's aico.json file and will default to English if no specific language is configured.

When is the best time to use the /pm.clarify command?

You should use it whenever requirements feel 'unclear', when you encounter conflicting details in a task, or before starting development on a complex feature.

How does this skill prevent overwhelming the user?

The skill strictly enforces a 'one question at a time' rule, limiting clarification sessions to a maximum of five high-priority questions to ensure focus and clarity.

Does it provide expert advice or just ask questions?

It provides both. For every ambiguity identified, it presents multiple options with trade-offs and specifically recommends the best path forward with reasoning.

What happens after I answer a clarification question?

Once an option is selected, the skill is designed to immediately update your project documentation (typically in docs/reference/pm/) to reflect the new decision.

AI PM Requirement Clarifier

Name: AI PM Requirement Clarifier
Author: yellinzero

byyellinzero

Collaboration Tools

Resolves requirement ambiguities through structured, one-at-a-time questioning and expert recommendations.

About

The AI PM Requirement Clarifier skill transforms Claude into a disciplined Product Manager that eliminates project ambiguity before a single line of code is written. By enforcing a structured process of asking exactly one question at a time with comparative options and expert reasoning, it prevents stakeholder overwhelm while ensuring all technical gaps, edge cases, and security concerns are addressed. This skill is essential for refining vague user stories, resolving conflicting logic, and automatically documenting project decisions to keep development teams aligned and efficient.

Key Features

Structured options table featuring detailed trade-offs and implications
Automated priority sorting focusing on high-impact scope and security issues
0 GitHub stars
Single-question flow to prevent cognitive overload during requirement gathering
Expert-led recommendations with logical reasoning for every decision point
Real-time documentation updates to capture decisions within project reference files

Use Cases

Defining clear acceptance criteria for vague or high-level user stories
Resolving conflicting business logic before starting feature development
Filling information gaps regarding data structures and edge-case handling

About

Key Features

Structured options table featuring detailed trade-offs and implications
Automated priority sorting focusing on high-impact scope and security issues
0 GitHub stars
Single-question flow to prevent cognitive overload during requirement gathering
Expert-led recommendations with logical reasoning for every decision point
Real-time documentation updates to capture decisions within project reference files

Use Cases

Defining clear acceptance criteria for vague or high-level user stories
Resolving conflicting business logic before starting feature development
Filling information gaps regarding data structures and edge-case handling