onboarding

Orchestrates an eight-phase workflow that bootstraps a Playwright e2e test suite from zero.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @civitas-cerebrum/element-interactions, @civitas-cerebrum/achilles, playwright.

What problem does it solve? Taking a project with no end-to-end tests to a maintained Playwright suite normally requires ad-hoc decisions about scaffolding, journey discovery, coverage, and reporting. This Skill defines a gated eight-phase workflow so an agent (or human) can run the full bootstrap deterministically, with enforced exit criteria between phases. ## Core Features & Use Cases - Eight-phase pipeline: scaffold, groundwork, happy-path, journey-mapping, coverage-expansion, bug-discovery, secrets-sweep, and report, each with explicit exit criteria and per-deliverable commits. - State-machine enforcement: a status ledger at tests/e2e/docs/onboarding-status.json plus workflow-reviewer subagents gate every phase, pass, and cycle transition, blocking silent phase skips. - Dual run modes: interactive use inside Claude Code or hands-off execution from an external automated CLI driver, with standard vs depth strictness levels. - Use Case: Point the agent at a running web app with no tests; it scaffolds Playwright config, maps user journeys, writes specs per priority tier, runs adversarial bug hunts, sweeps secrets into .env, and produces a QA summary deck. ## Quick Start Ask the agent to onboard this project and automate your app's URL from zero, then choose standard or depth run mode when prompted.

Frequently Asked Questions about onboarding

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

FAQPage Schema
How do I add e2e tests to a project that has none?▼

Run the onboarding workflow, which scaffolds Playwright config, maps user journeys, writes one spec per journey, and finishes with a secrets sweep and summary deck. Each of the eight phases has explicit exit criteria before the next begins.

How to automate Playwright test suite creation with an AI agent?▼

Invoke the onboarding skill interactively in Claude Code or from an external automated CLI driver. The agent dispatches role-scoped subagents per phase and a workflow-reviewer approves each transition against a status ledger.

Can I resume an interrupted onboarding run?▼

Yes. Find the latest completed phase from tests/e2e/docs/journey-map-coverage.md and the commit history, then restart from the next phase. Automated drivers typically expose a --resume flag that reads the onboarding-status.json ledger.

What is the difference between standard and depth run modes?▼

Standard mode runs the first pass strictly parallel and relaxes later passes, suiting everyday onboarding. Depth mode enforces strict per-journey parallel dispatch on every pass and cycle, costing up to roughly 20x more subagent dispatches and tokens.

When should I not use this onboarding workflow?▼

Skip it when the project already has a Playwright suite with substantial coverage, since onboarding is designed for zero-to-suite bootstrap, not augmentation. If tests/e2e/ already contains committed specs, run the relevant phase skill directly instead.