skills.rest
alfredolopez80
alfredolopez80COMMUNITY
Explore all skills by this author →
Website𝕏@alfredolopez80GitHub

clarify

Plan and execute structured requirement clarification using the AskUserQuestion workflow.

145|21|Updated Jan 2, 2026
Search Tags:#planning#requirements#stakeholders#clarify#feature-design#ask-user-question
One-click install
npx skills add https://github.com/alfredolopez80/multi-agent-ralph-loop --skill clarify-alfredolopez80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/alfredolopez80/multi-agent-ralph-loop/tree/main/.claude/skills/clarify
Command: npx skills add https://github.com/alfredolopez80/multi-agent-ralph-loop --skill clarify-alfredolopez80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines collecting complete, unambiguous requirements by guiding users through a structured AskUserQuestion workflow that captures MUST_HAVE (blocking) and NICE_TO_HAVE (optional) information before implementation.

Core Features & Use Cases

  • Structured questioning workflow that enforces MUST_HAVE and NICE_TO_HAVE capture
  • Pre-implementation validation gates to prevent scope creep
  • Templates and guidance for downstream planning, testing, and deployment
  • Use cases include starting new features with ambiguous specs, resolving conflicting requirements, and aligning stakeholder expectations across teams

Quick Start

Run /clarify to begin intensive requirement gathering for the current task.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I clarify ambiguous requirements before starting feature implementation?▼

To clarify ambiguous requirements, use a structured questioning workflow that captures MUST_HAVE blocking and NICE_TO_HAVE optional information. This enforces disciplined validation gates to prevent scope creep before development begins.

What is the best way to align stakeholder expectations during feature design?▼

Align stakeholder expectations by executing structured requirement clarification that distinguishes blocking from optional information. This resolves conflicting requirements and enforces validation gates before implementation planning proceeds.

How do I prevent scope creep when gathering specifications for a new feature?▼

Prevent scope creep by applying pre-implementation validation gates during requirement gathering. The structured questioning workflow isolates MUST_HAVE blocking needs from NICE_TO_HAVE optional requests to enforce strict scope boundaries.

Can I use structured requirement gathering for evaluating multiple approaches?▼

Yes, structured requirement gathering applies when evaluating multiple approaches or confronting ambiguous specs. It guides users through an intensive AskUserQuestion workflow to collect complete requirements before committing to a specific implementation path.

Does requirement clarification provide templates for downstream planning and testing?▼

Yes, requirement clarification provides templates and guidance for downstream planning, testing, and deployment. It establishes integration points after collecting blocking and optional information to support subsequent development phases.

Related Skills

Explore More Product & Management Skills→
motoki317motoki317
4

Requirements Definition

Define structured project requirements with acceptance criteria and traceability.

Community
Advanced
ljucaskljucask
1

pm-prd

Synthesize validated product strategy inputs into a structured Product Requirements Document.

Community
Advanced
tonehqtonehq
11

generate_feature_prd_and_implementation

Generate a formal feature PRD with requirements, edge cases, and API design into a Markdown file.

Official
Advanced
crozzbitecrozzbite

socratic-mvp

Identify MVP scope and architectural boundaries through guided questioning.

Community
Advanced