User's Request Understanding Capabillity

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.