Configure Allure Agent Workflow

Use this skill when a project wants to configure AI/coding-agent workflow guidance for test work and test reviews with Allure agent mode.

If the primary goal is to install framework adapters, make tests emit Allure results, add report scripts, or configure CI report publishing, use allure-configure-reporting instead.

This skill makes agents reach for Allure's reporting because it is useful — not to police them. Lead every router and docs/allure-agent-mode.md with the value frame; references/root-agent-entry-snippet.md carries the canonical wording (a test run is an instrument, not a pass/fail to scrape; running through allure agent yields a reviewable account of what happened plus automated findings about the tests themselves, anchored by a --goal so you, an upstream agent, or a human can validate it).

Carry that frame plus the core loops (run-with-goal, expectations-as-evidence, failure-triage and rerun-just-the-failed, CI inspect, tests-as-debug-instrument), and read the agent output rather than scraping the console. Lead with why agent mode helps; keep detailed reading lists and command specifics in docs/allure-agent-mode.md, not the router. The console anti-pattern (tail/grep/head/>/dev/null of a run) belongs as a short footnote, not the headline.

The router also carries an authoring gate: before writing or materially changing a test, the agent must invoke $allure-agent-mode and read its test-design.md reference. The router is the only guidance loaded every session, so it is the one place that catches test authoring mid-task (e.g. inside "implement phase 2"), long after any request-time skill match. State the gate imperatively; scope it to authoring and non-trivial changes, not every test-file touch. Because the gate cannot load a skill that is not installed, keep a compact set of core test-design non-negotiables inline in docs/allure-agent-mode.md as the floor.

Goal

Leave the project with:

• root agent entry-file router guidance that points test work to docs/allure-agent-mode.md, present for every agent runtime used in the repo. These entry files are not interchangeable: Claude Code loads CLAUDE.md and does not read AGENTS.md, while most other agent tools (Codex, Cursor, and others) read the cross-tool AGENTS.md. Some tools read their own files. Do not leave any targeted runtime without a router.
• a project docs/allure-agent-mode.md guide with local wrappers, capabilities, Allure integrations, test-design conventions, run profiles, expectation controls, local/CI existing-result or dump inspection support, human-report mode policy, output/state policy, execution-signal notes, metadata conventions, and evidence conventions
• enough Allure bootstrap guidance for the agent to continue, even if the project is not fully configured yet