brse-spec-transferlisted

# BrSE Spec Transfer Use this skill when moving or rewriting specification content between planning and delivery surfaces. ## When To Use - Moving a customer Japanese document into a dev surface (Outline, Plane, Backlog, GitHub). - Converting a Markdown spec into a Plane/Backlog ticket while preserving headings, tables, task IDs. - Producing a JP demo/customer document from an internal English/Vietnamese working draft. ## When NOT To Use - The spec has not been verified — run `brse-spec-verify` first. - The transfer needs new ticket breakdown — use `brse-ticket-breakdown` (transfer preserves structure, breakdown changes it). - The translation requires inferring intent — invoke `brse-intent-reader` before transfer to surface implicit content. - Source contains content that should not be visible to the target audience — escalate, do not auto-filter. ## Workflow 1. Identify the source surface and target surface. 2. Preserve the source structure unless the user explicitly requests a new structure: - headings - bullets - tables - separators - task IDs - links - screenshots or image placeholders - section order 3. Translate visible customer-facing wording into Japanese when the target is a Japanese demo/customer document. 4. Keep established system/product terms unchanged. 5. Link only the task ID token when the title contains a task ID plus text. 6. Separate requirement content from AI/reference notes. ## Output Shape When drafting a task/ticket: