onboard-product
Skill2 starsChanged 8 days agoApache-2.0View on GitHub
Onboard a single product inside an existing project into products/<PRODUCT>/ — PRODUCT.md deltas, routing (JIRA component/label → product) in PROJECT.md, feature/test-method matrix. Use for "/onboard-product", "Produkt einrichten", or when a JIRA project covers several products. Not for a project's first onboarding — /onboard-project.
- Reads credentials
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-testingSkill
- agentswitchSkill
- api-testingSkill
- bug-reportSkill
- bug-reproductionSkill
- demoSkill
- deploy-to-stageSkill
- exploratory-testingSkill
- failure-analysisSkill
- model-setupSkill
- onboard-projectSkill
- perf-analysisSkill
- qa-helpSkill
- qa-metricsSkill
- qa-reportSkill
- re-boardSkill
- reconSkill
- release-readinessSkill
- report-to-jiraSkill
- retest-bugSkill
- retro-learnSkill
- risk-based-testingSkill
- scaffold-suiteSkill
- security-testingSkill
- skill-reviewSkill
- test-automationSkill
- test-case-managementSkill
- test-reliabilitySkill
- test-ticketSkill
- visual-testingSkill
- webdriverio-testingSkill
- whats-newSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 25
First product in this project?: If projects/<KEY>/products/ does not exist yet, state the consequence plainly and get an explicit yes: …
- Distinctive: line 35
Routing: Ask which JIRA components and/or labels identify this product's tickets.
- Very specific: line 72
Bridge file: write .agents/qa-project-context/<KEY>/<PRODUCT>.md as the
- Very specific: line 83
Final checks: every registry row has a directory and every directory has a registry row (nothing else enforces this — for projects, JIRA is …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
/onboard-product — teach the agent one product of a project
Expect 5–15 minutes, not the 30–60 of onboard-project: you only answer what
differs from the project. Every question defaults to "same as the project", and a
"same" answer writes nothing. That is the whole point of the layer — see
.claude/rules/core/product-layer.md.
Steps
- Target project: from the argument (
/onboard-product SHOP) or ask. Verifyprojects/<KEY>/PROJECT.mdexists — a product with nothing to inherit from is meaningless. If it doesn't, runonboard-projectfirst. - Product key + one-liner. Key is uppercase
[A-Z][A-Z0-9]{1,15}, unique in the project, and becomes the directory name. RejectSECRET,CREDENTIALS,ENVand anything containing them — the pre-tool guard (pre-tool-guard.sh/ opencode plugin) blocks paths matching*secrets*/*credentials*, so the directory would be unwritable with a confusing "refusing to write a secrets file" error. - First product in this project? If
projects/<KEY>/products/does not exist yet, state the consequence plainly and get an explicit yes: from now on every ticket in this project must route to a product or toproject-wide. Only then createproducts/and write the## Productssection intoPROJECT.md(registry table + match order + no-match policy + project-wide entries). This is the only write intoPROJECT.mdthis skill ever makes. - Copy the scaffold:
projects/_template/products/_template/→projects/<KEY>/products/<PRODUCT>/(plugin mode: read the scaffold from$CLAUDE_PLUGIN_ROOT/projects/_template/products/_template/) and write only into the consumer's repo. - Routing. Ask which JIRA components and/or labels identify this product's
tickets. Fetch the project's real component list via the Atlassian MCP and
let the user pick existing values instead of typing from memory — a dead routing
row fails silently and costs a whole session to notice. Write the row into the
PROJECT.mdregistry only, never duplicated intoPRODUCT.md. Note any component/label that belongs to no product (infra, CI) as aproject-wideentry. Then ask for the secondary signals worth recording, and only those that actually hold: code paths of this product in the repo, a fix-version pattern if products release separately, whether epics carry the product assignment. Skip any the user is unsure about — a wrong secondary signal routes silently and confidently. The table improves later on its own (.claude/rules/core/product-layer.md→ "Routing learns from being corrected"), so this does not have to be complete today. - The difference interview — one pass, section by section, each question phrased as "same as the project, or different?": Environments → Test users → Deploy runbook → Pipelines/gates → Reporting → Test assets → Gotchas. Delete every section the user leaves at "same".
- Feature & test-method matrix — always asked, never inherited. Walk the fixed
row list yes/no. For each
yes, propose the scaffold's default test types and responsible skill, and let the user adjust. This is the longest step and the one that paysqa-managerback on every later ticket. - Test users: vault paths only, never a password in this conversation. Secret
keys per
.claude/rules/core/product-layer.md→ Naming (<KEY>_<PRODUCT>_<ROLE>_PASSWORD). The product inherits the project's Secrets source unless it declares its own — only ask when this product genuinely differs. Onkeychain: hand the user the one-time command per key (security add-generic-password -s <SECRET_KEY> -a qa -w), then run the blueprint'sresolve-secrets.sh. Onenv-file: tell the user to add the keys to.env.playwright-secretsthemselves — it is gitignored, and the the pre-tool guard blocks any write to it, so do not attempt it. - Generate the "Differences from the project" index at the top of
PRODUCT.mdfrom what was actually written. Derived last, never hand-maintained. - Seed
products/<PRODUCT>/learnings.mdfrom the scaffold. Move any gotcha that is really product-specific out of the project'slearnings.mdinto it. Also seedproducts/<PRODUCT>/flow-map.mdfrom the scaffold (empty area skeleton —retest-bugscopes regression sweeps from it onceretro-learnhas promoted the first flows). - Bridge file: write
.agents/qa-project-context/<KEY>/<PRODUCT>.mdas the merged projection — project base with the product's deltas already resolved, self-contained, because the vendored skills read one flat file and never inherit. Include the frontmattergenerated_from:(both source paths) andsource_sha:so staleness is checkable instead of remembered. Whenproducts/<PRODUCT>/flow-map.mdexists, append only its confirmed Areas as a## Flow mapsection, never Unconfirmed candidates, and add the map togenerated_from:/source_sha:— same rule for the project-levelflow-map.mdin.agents/qa-project-context/<KEY>.md. memory/INDEX.md: extend the project's existing row with the product list. One row per project, never one row per product.- Final checks: every registry row has a directory and every directory has a
registry row (nothing else enforces this — for projects, JIRA is the authority;
for products there is none). Flag all remaining
TODO:s. Read the resultingPRODUCT.mdback as a summary and ask for corrections.
What this skill never does
Invent a routing component or label. Copy a value from PROJECT.md into
PRODUCT.md "for completeness" — that breaks inheritance and doubles the
maintenance surface. Create products/ for a project the user has not confirmed is
multi-product. Write into .env.playwright-secrets. Restate JIRA transitions or the
report format in PRODUCT.md — those are sealed and read from PROJECT.md only.
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.

