brse-intent-readerlisted

# BrSE Intent Reader Use this skill when the Japanese customer input is literally short but likely carries unstated expectations. The goal is "行間を読む" — read between the lines — without fabricating requirements. ## When To Use - Customer message is unusually short for the change being requested. - Customer uses polite/hedged phrasing ("〜していただけますと幸いです", "ご検討ください") around something operationally important. - A spec change request that doesn't mention obvious side effects. - "前回と同様で" / "いつもの通りで" without specifying what "usual" means. - Customer asks a question that implies a complaint. ## When NOT To Use - Customer message is already explicit and complete — running this skill adds inference where none is needed. - The reading-between-lines would produce scope/cost change — those must be confirmed by the customer, not assumed. - Input is from a developer, not a Japanese stakeholder — culture and politeness signals do not transfer. - Customer has stated their request directly and you would be inventing additional demands — stop and run `brse-requirement-clarifier` on the literal request. ## Workflow 1. Read the literal message and write down what is **explicitly** stated. 2. Identify signals that suggest unstated content: - Hedging language softening a real demand. - Omitted scope that is normally specified. - References to past behavior or other projects without detail. - Mismatched politeness level (suddenly formal = pressure, suddenly casual = trust or frustra