brse-dev-triagelisted

# BrSE Dev Triage Use this skill when a developer asks the BrSE a question that the spec or ticket does not fully answer. The BrSE must decide: answer now, trace source first, or escalate to customer — and reply in a way that does not block the dev unnecessarily. ## When To Use - Dev asks "Spec này có nghĩa là gì?" / "実装どっちが正しい？" / "Edge case này xử lý sao?" - Dev finds that source behavior conflicts with spec. - Dev needs a decision that the BrSE is not authorized to make alone. ## When NOT To Use - Question is about implementation technique only (e.g., "how to write this query") — that is dev mentoring, not BrSE triage. - Question is from a customer to the BrSE — use `brse-requirement-clarifier`. - Question is about a pure spec ambiguity that has not been triaged through the spec itself — run `brse-spec-verify` against the spec first. - "Question" is actually a complaint about workload — escalate to PM, not to customer. ## Categorization Flowchart ```dot digraph dev_triage { rankdir=TB; node [shape=box, style=rounded]; start [label="Dev question arrives", shape=oval]; q1 [label="Is the answer literally in\nspec / ticket / source comment?", shape=diamond]; q2 [label="Does the answer depend on\ncurrent code behavior?", shape=diamond]; q3 [label="Does the answer commit\nto a business rule?", shape=diamond]; q4 [label="Does the question reveal\na missing requirement?", shape=diamond]; cat1 [label="Cat 1: Answerable\nfrom spec/ticket\n→ B