business-explain
Skill0 starsChanged 5 days agoMITView on GitHub
Use this when a feature, screen or business flow must be explained to someone who does not know the system — a new member, a manager, a sales person or a non-technical client — in plain words, from the project's documents (doc-to-md output) and/or code, with every statement traceable to its source.
In this repository24 other files it gives its agents.
- anatomySkill
- approachSkill
- brainstorm-brseSkill
- change-impactSkill
- code-to-businessSkill
- cross-checkSkill
- detail-design-jpSkill
- diagramSkill
- doc-to-mdSkill
- e2e-test-playwrightSkill
- estimationSkill
- excel-analyzeSkill
- image-analyzeSkill
- jp-vi-translateSkill
- meeting-intakeSkill
- proposal-genSkill
- qa-tone-brseSkill
- report-genSkill
- research-jp-techSkill
- review-gateSkill
- scope-analysisSkill
- testcase-review-jpSkill
- test-designSkill
- verify-outputSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Run <py> ${CLAUDE_PLUGIN_ROOT}/scripts/brse.py config and read its JSON:
- Very specific: line 35
Collect facts with sources: Read .brse/knowledge/docs/ (run doc-to-md first if missing).
- Very specific: line 55
Plain-language check: no sentence over ~25 words for non-tech.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Before running
<py> below = the Python recorded by /brse-toolkit:setup (runtime.python
in ~/.config/brse-toolkit/config.json — read that file directly), else the
first of python3, python, py -3 that runs. No Python at all → tell the
user to run /brse-toolkit:setup, and continue only with steps that need no
script, saying which checks were skipped.
Run <py> ${CLAUDE_PLUGIN_ROOT}/scripts/brse.py config and read its JSON:
error→ show it to the user and stop; the config file must be fixed first.workspace_rootis null → the folder isn't initialized. Ask once: run/brse-toolkit:initfirst (recommended — memory and knowledge get saved for next time) or continue once without saving. Running as a subagent dispatched by a main agent → the parent already resolved this; proceed.- Otherwise use
config.paths(sources,templates,outputs— relative toworkspace_root),config.style,config.translation, and the files in.brse/memory/long/. Never assume a folder name the config doesn't list. warningsnot empty → mention them in one line (likely a typo in the config).
When to use
"Explain what this feature does", onboarding a new member, a summary for a
manager or client who doesn't read specs. For a technical explanation from
code for developers, use code-to-business.
Steps
- Reader first. Pick one: non-tech (client/manager/sales), new member (knows software, not this system), new developer. State it at the top; it decides vocabulary and depth. Output language from the request or config.
- Collect facts with sources. Read
.brse/knowledge/docs/(rundoc-to-mdfirst if missing); for behaviour only visible in code, runcode-to-businessand reuse its cited facts. Every fact keeps its source (file + sheet/heading/row, or file:line). Gaps → "cần xác nhận / 要確認", never filled by guessing. - Write in this order (draft facts only — wording is done by Comtor):
- In one sentence: what it is for and who uses it.
- Why it exists: the business problem it solves.
- Who and when: roles, triggers, frequency.
- Step by step: the business flow in plain words, one action per step, no field IDs or table names for non-tech readers.
- A real-life example: one concrete scenario with sample values from the spec (say they are examples).
- Rules that matter: limits, validations, statuses, what is blocked and why — as "if … then …".
- Glossary: every term the reader would trip on → plain meaning (project glossary first).
- FAQ / what to watch out for and the open questions.
Optional: a simple flow diagram (ask System Engineer,
diagramskill,floworflow-lanestype) — at most ~10 boxes for non-tech readers.
- Plain-language check: no sentence over ~25 words for non-tech; no unexplained acronym; no screen/table/variable names unless the reader is a developer. Every paragraph still has its source tag.
- Wording: send the draft + sources + reader + language to Comtor; check back that no fact, number or rule changed meaning.
Output
The explanation (Markdown, or Word/Slide via report-gen when asked),
saved in config.paths.outputs, with the source list at the end and the
open questions inline in the reply.
Handoff
Finish with review-gate (runs verify-output).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

