brse-skill-authorlisted

# BrSE Skill Author ## Overview Bootstrap and maintain skills inside this plugin so that future BrSE sessions can discover and reuse them reliably. **Core principle:** A skill is a reusable BrSE technique, not a war story about one customer. If the same situation has not appeared at least twice, it does not need a skill yet — capture as a note instead. ## When To Use - Adding a new skill to `plugins/brse-workflow/skills/`. - Editing an existing skill's frontmatter, Overview, Rules, or Example block. - Reviewing a contributed skill before merge. - A BrSE pattern has repeated across sessions and you want to convert it into a permanent skill. - The discovery rate of an existing skill is too low — its description or naming needs to be re-audited. ## When NOT To Use - One-off solutions that will not repeat — capture as a project note instead. - Customer-specific glossary terms or product knowledge — those belong in the project glossary, not in a generic skill. - General coding conventions — those belong in repo `AGENTS.md` / `CLAUDE.md`. - A skill that already exists and just needs a content fix — edit it directly; this skill is for *authoring discipline*, not every minor change. ## Inputs 1. **Intent**: What BrSE situation does the new (or edited) skill address? State it as a triggering condition, not a capability list. 2. **Baseline evidence**: At least one realistic BrSE input (JP customer message, dev report excerpt, ticket text) that would trigger the skill. 3. **Ref