neo-clarificationlisted

# Requirement Clarification Specifications Apply the Inversion & Generator Pattern. Follow this protocol strictly to translate raw, chaotic user complaints and screenshots into clean, structured system specifications. --- ## 1. Perceive Phase 1. **Information Extraction**: - Carefully read the user's text and inspect any attached screenshots or logs. - Filter out emotional noise, frustrations, and blame. - Separate objective facts (what is currently happening or visible) from user expectations (what they wanted to accomplish). 2. **Identify System Boundaries**: - Determine the scope, domain, and potential technical layers affected by the feedback (e.g., frontend rendering, network APIs, database states, permission groups). --- ## 2. Reason Phase 1. **Load Analysis Framework**: - **Always read** the external analysis guide before starting your deduction: [5w1h-framework.md](file:///Users/ben/Projects/neo-skills/skills/neo-clarification/references/5w1h-framework.md) 2. **Context Reconstruction (5W1H)**: - Map the extracted facts to the 5W1H framework (Who, Where, When, What, Why, How). - Formulate logical hypotheses on the root causes of UI anomalies or system behaviors. 3. **Identify Gaps**: - Pinpoint critical missing information (e.g., browser environment, specific action steps, parameters, error logs). - Prepare a list of clarifying questions to ask the user. --- ## 3. Act Phase Generate a structured "Requirement Translation a