agentleFS
upex-galaxyupex-galaxy/agentic-qa-boilerplate/.agents/skills/business-e2e-context/SKILL.md

business-e2e-context

Skill26 starsChanged 9 days agoMITView on GitHub

How people actually use the system under test end to end: the personas, the user journeys first (entry point, steps, branches, where money or data changes hands, where it can fail), then the feature catalog those journeys cross and the flows that span several features. Load it whenever a task touches an E2E or UI test, a user flow, a smoke or regression scope, an exploratory session, a story's place in a bigger journey, or asks what a user can do in the product, even when nobody says 'feature map' or 'journey'. Reads its map through `bun run context:map business-e2e-context`. Pure knowledge plus a self-update proposal path: NOT for running a QA stage, NOT for entities (business-data-context) or endpoint contracts (business-api-context).

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    DO: read the map through bun run context:map business-e2e-context (or --section <id> for one journey or feature).

    line 18
  2. Very specific:

    DO: treat a placeholder map as "no map".

    line 19
  3. Distinctive:

    DO: start from the journey, then the feature.

    line 20
  4. Distinctive:

    WHEN a session observes something that contradicts a section (a step, a branch, a state the UI shows): PROPOSE the one-section edit with …

    line 21
  5. Very specific:

    DO NOT: write anywhere but this skill's own references/.

    line 22
  6. Very specific:

    DO NOT: copy map content into this SKILL.md.

    line 23
  7. Very specific:

    Before a step that uses diagrams (redrawing a figure), run the point-of-use check in agentic-qa-core/references/preflight-gate.md §8.

    line 24

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

business-e2e-context

Kind context with a declared write scope (agentic-qa-core/references/skill-composition-strategy.md §2b). Delivered once by upstream as a placeholder, then owned by the project: the map inside is this project's synthesis. Procedure: agentic-qa-core/references/business-context-maps.md.

Compact Rules

  • DO: read the map through bun run context:map business-e2e-context (or --section <id> for one journey or feature). NEVER read references/business-e2e-map.html raw: its SVG is most of the bytes and none of the facts.
  • DO: treat a placeholder map as "no map". Say so and hand the user project-context mode e2e; never plan E2E coverage as if the product had no journeys.
  • DO: start from the journey, then the feature. A story is tested inside the journey that reaches it; the feature catalog answers "what exists", the journeys answer "what a user does and where it breaks".
  • WHEN a session observes something that contradicts a section (a step, a branch, a state the UI shows): PROPOSE the one-section edit with its evidence to the user (or to the conductor when you are a supervised worker), apply it only on approval. Procedure: references/refresh.md.
  • DO NOT: write anywhere but this skill's own references/. No Jira, no .context/, no other skill, no test code, no product code.
  • DO NOT: copy map content into this SKILL.md. Judgment goes in ## Rules or references/gotchas.md, dated and measured.
  • Before a step that uses diagrams (redrawing a figure), run the point-of-use check in agentic-qa-core/references/preflight-gate.md §8.

Read full SKILL.md when: building a briefing for a UI or E2E dispatch, scoping a smoke or regression run, deciding whether a section is stale, or proposing an edit to the map.

What this skill knows

One aspect of the system under test: its use, end to end. Who the users are, which journeys they take and where each one can fail, which features exist and which journeys cross them, and the flows that only make sense across several features. Loading it changes what the agent KNOWS; the only thing it ever does is propose an edit to its own map.

Sources of truth (cited, never copied)

SourceWhat lives thereRole
references/business-e2e-map.htmlthe synthesis: a <section> per journey first, then per feature, plus discovery-gapsthis skill's map (read via bun run context:map)
the frontend repo ({{FRONTEND_REPO}})routes, pages, forms, guardswins over the map on any conflict
the running app of the active environmentwhat a user really seeswins for behaviour
business-data-context, business-api-contextthe data and API behind each stepcited per step, never restated
project-context mode e2ethe generator that CREATEs the map and UPDATEs its stale sectionsowns regeneration

Rules (judgment, dated)

(none yet: each rule carries YYYY-MM-DD · rule · measured: how)

Not here

  • Entities, triggers and state machines → business-data-context.
  • Endpoint groups, auth and error semantics → business-api-context.
  • Selectors, page objects and test code → tests/components/ (KATA), owned by /test-automation.
  • Jira stories and their ACs → .context/PBI/ (synced cache).

References

  • references/business-e2e-map.html — the map (generated; read through the reader).
  • references/refresh.md — the self-update procedure and this aspect's staleness signals.
  • references/gotchas.md — measured traps in reading this project's journeys.

Refinements

Lessons land as proposals per agentic-qa-core/references/skill-refinement-protocol.md, never as direct edits.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.