nguyenthe-hien
UserBrSE workflow skills for Japanese-offshore software delivery. 13 cross-platform skills (Claude Code, Desktop, Cowork web, Codex CLI) for requirement clarification, source impact tracing, structured thinking (MECE/Pyramid), Japanese client reporting, and more.
Categories
Indexed Skills (16)
brse-client-report
Use when a BrSE must produce or polish a Japanese customer-facing report and the wording, tone, conclusion-first structure, and business style must be ready for a Japanese stakeholder reviewer.
brse-dev-triage
Use when a developer asks the BrSE a question that the spec or ticket cannot fully answer, when source behavior conflicts with spec, or when a dev is blocked waiting for a decision the BrSE alone cannot make.
brse-feasibility-challenge
Use when a customer or PM request would set the project up to fail if relayed as-is — impossible timeline, conflicting architecture, known failure mode, or contradiction with a prior commitment — and the BrSE must push back without breaking customer trust.
brse-impact-trace
Use when a BrSE must answer an impact or feasibility question that needs evidence from the actual codebase — frontend route, backend controller, API contract, DB schema, batch job, or tenant config — before reporting to a customer or PM.
brse-intent-reader
Use when a Japanese stakeholder message is unusually short, uses polite hedging around something operationally important, omits scope that is normally specified, or references past behavior without detail — situations where 行間を読む is required before clarifying.
brse-qa-scenario
Use when a BrSE is preparing a Japanese QA sheet, regression checklist, demo case set, or release verification plan from a clarified requirement and acceptance criteria.
brse-report-reviewer
Use when a developer, AI engineer, QA, or offshore team member has submitted a report and the BrSE must verify its substance and clarity before forwarding to a Japanese customer or PM — daily status, investigation, impact analysis, spike result, or release-gate QA.
brse-requirement-clarifier
Use when a BrSE receives a vague Japanese or bilingual stakeholder request that mixes goal, constraint, and example without clear scope, or inherits a partial spec that still has gaps before it can be forwarded to dev.
brse-skill-author
Use when adding, editing, or reviewing a BrSE skill in this plugin — the description field needs an objective check, the SKILL.md is missing required blocks, or a new BrSE workflow pattern has appeared more than twice in recent sessions and is worth capturing as a skill.
brse-spec-transfer
Use when a BrSE needs to move spec content from a customer Japanese document into a dev delivery surface (Outline, Plane, Backlog, GitHub) or the other direction, and the structure, task IDs, tables, and product terms must survive the move intact.
brse-spec-verify
Use when a BrSE requirement document is about to be forwarded to dev or transferred to a delivery surface, when a sprint-planning doc is inherited from another BrSE, or when a developer pushes back that a spec is unclear and the BrSE needs an objective check.
brse-structured-thinking
Use when a BrSE deliverable needs structural thinking — customer hands over a solution instead of a problem, bug needs root cause, investigation needs hypothesis evidence, release decision needs failure-mode and reversibility check, report has buried conclusion, scope has silent gaps or overlapping tickets, broad customer question needs splitting, vague "なんとなくおかしい" needs decomposition, or inherited spec carries unverified assumptions. Not for already-clean deliverables.
brse-ticket-breakdown
Use when a BrSE has a clarified requirement that must become executable work for offshore developers and QA, and the split into tickets must respect independently verifiable behavior rather than vague technical layers.
brse-workflow-chain
Use when a BrSE receives a new customer request and does not yet know which combination of BrSE skills to run, or when a session risks skipping a needed step between clarify, verify, trace, breakdown, QA, and customer reply.
brse-skill-name
Use when [specific triggering symptoms — what the BrSE is facing, not what this skill does]. Keep ≤500 characters, third person, no workflow summary, no "→" / "stage" / "first... then" patterns.
brse-offshore-sync
Use when a BrSE must keep distributed teams aligned across language, timezone, role, and context gaps — before a customer meeting, after a standup, during release readiness, or when handing off context between BrSEs.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.