skills.rest
Rafael-Rueda
Rafael-RuedaCOMMUNITY
Explore all skills by this author →
GitHub

User's Request Understanding Capabillity

Clarify ambiguous user requests with structured select box options.

Updated Dec 22, 2025
Search Tags:#specification#requirements#clarification#decision-making#user-stories#technical-architecture#project-scoping
One-click install
npx skills add https://github.com/Rafael-Rueda/sardius --skill user-s-request-understanding-capabillity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: User's Request Understanding Capabillity
Source: https://github.com/Rafael-Rueda/sardius/tree/main/.claude/skills/request_understander
Command: npx skills add https://github.com/Rafael-Rueda/sardius --skill user-s-request-understanding-capabillity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the frustration of vague or incomplete user requests that lead to wasted time and incorrect implementations. It ensures you get exactly what you need by systematically extracting clear, actionable requirements before any work begins.

Core Features & Use Cases

  • Structured Decision Extraction: Uses the "Select Box Pattern" to present clear options instead of asking open-ended questions.
  • Two-Round Clarification: Goes deeper into chosen alternatives to uncover hidden requirements.
  • Trade-off Transparency: Each option includes brief pros/cons so you can make informed decisions.
  • Use Case: When a user asks "Build a login system," this Skill prevents assumptions by asking structured questions about authentication strategy, session management, and JWT algorithms, ensuring the final implementation matches their exact needs.

Quick Start

Activate this skill when you need to clarify a user's request. For example, if someone asks "Add user management," you would respond with structured options like:

⚠️ Clarification Needed: User Management Scope

1. User Roles

  • [ ] A. Basic (User/Admin): Simple two-tier system (Easy to implement, limited flexibility).
  • [ ] B. Role-Based (RBAC): Multiple roles with permissions (More control, complex setup).
  • [ ] C. Permission-Based: Granular per-action permissions (Maximum flexibility, highest complexity).

2. Profile Fields

  • [ ] A. Basic: Name, email, avatar (Quick setup, minimal data).
  • [ ] B. Extended: Address, phone, preferences (Comprehensive, more development).

Reply with your selections (e.g., "1A, 2B") or type "Recommended" to accept my defaults.

Frequently Asked Questions about User's Request Understanding Capabillity

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

FAQPage Schema
How do I clarify vague user requests before starting implementation?▼

Clarifying ambiguous requests extracts decision data by presenting structured options with trade-offs instead of open-ended questions. This prevents misaligned implementations by confirming scope, architecture choices, and edge-case handling upfront through a two-round iterative process.

What's the best way to handle feature requests missing implementation details?▼

Use structured decision extraction to present 2–4 viable options per missing variable, each with clear pros and cons. This approach surfaces hidden requirements around tech stack, MVP versus full feature scope, and technical architecture decisions before work begins.

How do I avoid assumptions when gathering requirements for a new feature?▼

Apply the Select Box Pattern to systematically extract requirements instead of guessing. Present options covering authentication strategy, session management, user roles, data scope, and complexity trade-offs, then conduct a second round of clarification on chosen alternatives.

Can I use this to scope project decisions between multiple technical approaches?▼

Yes. This skill handles scope decisions by isolating decision variables—like RBAC versus permission-based access control—and presenting trade-offs for each option. Two rounds of clarification ensure you capture all constraints before committing to architecture or tech stack choices.

What happens when a user request has multiple viable solutions?▼

The skill presents each solution as a structured option with transparent trade-offs: complexity, implementation time, flexibility, and maintenance burden. Users select their preference, then you dive deeper into edge cases and hidden requirements tied to that choice.

Related Skills

Explore More Software Engineering Skills→
ArabelaTsoArabelaTso
142

ambiguity-detector

Detect ambiguous language in software requirements and user stories.

Community
Intermediate
YangYuS8YangYuS8

brainstorming

Guide teams from vague ideas to concrete design specifications.

Community
Advanced
useblocksuseblocks
24

pharaoh-decide

Record design decisions as sphinx-needs directives with decided_by, alternatives, and rationale.

Official
Advanced
onejaejaeonejaejae
2

spec-interview

Interview non-technical stakeholders to produce structured requirements in markdown.

Community
Advanced