journey-mapping

Discovers web application pages and user flows via Playwright to produce a prioritized journey map.

5|2|Updated May 19, 2026
One-click install
npx skills add https://github.com/civitas-cerebrum/achilles --skill journey-mapping-civitas-cerebrum
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: journey-mapping
Source: https://github.com/civitas-cerebrum/achilles/tree/main/skills/journey-mapping
Command: npx skills add https://github.com/civitas-cerebrum/achilles --skill journey-mapping-civitas-cerebrum

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/cli, and includes references (resource) components.

What problem does it solve? Writing E2E tests without understanding the application leads to shallow coverage and blind spots. This Skill systematically crawls a live web app, identifies every user flow, and produces a prioritized journey map that serves as the blueprint for all downstream test composition. ## Core Features & Use Cases - Parallel page discovery: Crawls the live application breadth-first using playwright-cli subagents, recording pages, interactive elements, state variations, and gated routes into an app-context document. - Flow identification and prioritization: Derives user journeys from discovered pages, assigns P0–P3 business-impact tiers plus a defect-likelihood risk axis, and deduplicates overlapping flows into reusable sub-journeys. - Test infrastructure probe: Captures auth model, reset/seed endpoints, persistent banners, and mutation endpoints for downstream test optimization. - Use Case: Before composing any E2E tests for a new web app, run this Skill to generate a sentinel-marked journey-map.md that coverage-expansion and test-composer consume as their mandatory input. ## Quick Start Ask the agent to map the app and discover user journeys for your application URL before writing any tests.

Frequently Asked Questions about journey-mapping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover user journeys in a web app before writing E2E tests?▼

Run journey-mapping to crawl the live app with playwright-cli, identify flows from discovered pages, and prioritize them into a journey-map.md. The map becomes the mandatory blueprint for downstream test composition.

What tool does journey mapping use for page discovery?▼

Discovery runs exclusively through @playwright/cli in live browser sessions, with parallel subagents per entry point. Static analysis, source reading, curl, and MCP browser tools are explicitly forbidden.

Can journey mapping handle pages behind login or paywalls?▼

Yes. Agents self-credential when signup is open or credentials are discoverable; otherwise gated routes are recorded under a Gated Areas section with the credentials needed, and deferred to coverage-expansion.

How are journeys prioritized in the journey map?▼

Each journey gets a P0–P3 tier based on business impact, plus an orthogonal risk axis derived from eight defect-likelihood factors. Risk orders dispatch within a tier but never changes the priority tier itself.

What happens if a journey-map.md already exists?▼

The skill checks line 1 for its generated sentinel. If present, it resumes and updates the existing map; if absent, it asks the user whether to rename the foreign file or use a different path.