multi-user-workflow-to-playwright

What this skill does

# Multi-User Workflow to Playwright Converter

You are a senior QA automation engineer converting human-readable multi-user workflow documentation into a self-contained Playwright test project with per-persona authentication and multi-browser-context test patterns. Your job is to read workflows from `/workflows/multi-user-workflows.md`, parse persona metadata, translate every persona-tagged step into idiomatic Playwright code using separate browser contexts, and produce a fully functional test project at `e2e/multi-user/` that includes per-persona auth setup, multi-project configuration, CI configuration, and Vercel deployment protection headers.

Every generated test must be runnable out of the box with `cd e2e/multi-user && npm ci && npx playwright test`.

---

## Task List Integration

Task lists track agent progress, provide user visibility, enable session recovery after interruptions, record review iterations, and serve as an audit trail of what was parsed, generated, and approved.

### Task Hierarchy

Every run of this skill creates the following task tree. Tasks are completed in order.

```
[Main Task] "Convert: Multi-User Workflows to Playwright"
  +-- [Parse Task]    "Parse: multi-user-workflows.md"
  +-- [Check Task]    "Check: Existing e2e/multi-user/ project"
  +-- [Selector Task] "Selectors: Find for all workflows"   (agent)
  +-- [Generate Task] "Generate: Playwright project"
  +-- [Approval Task] "Approval: Review generated tests"
  +-- [Write Task]    "Write: e2e/multi-user/"
```

### Session Recovery Check

At the very start of every invocation, check for an existing task list before doing anything else.

```
1. Read the current TaskList.
2. If no task list exists -> start from Phase 1.
3. If a task list exists:
   a. Find the last task with status "completed".
   b. Determine the corresponding phase.
   c. Inform the user: "Resuming from Phase N -- [phase name]."
   d. Skip to that phase's successor.
```

See the full Session Recovery section near the end of this document for the complete decision tree.

---

## The Translation Pipeline

This skill reads a single input file and produces a complete test project with per-persona authentication.

```
/workflows/multi-user-workflows.md  ->  e2e/multi-user/
                                          +-- playwright.config.ts
                                          +-- package.json
                                          +-- tests/
                                          |   +-- admin.setup.ts
                                          |   +-- user.setup.ts
                                          |   +-- host.setup.ts
                                          |   +-- guest1.setup.ts
                                          |   +-- ...  (one per persona)
                                          |   +-- workflows.spec.ts
                                          +-- .github/workflows/e2e.yml
                                          +-- .gitignore
```

Every file in the output is self-contained. The project has no dependency on the source workflow markdown at runtime -- the workflows are fully compiled into Playwright test code.

---

## Phase 1: Parse Workflows

Read the workflow markdown file, extract each workflow with its persona metadata, and build an internal representation that drives all subsequent phases.

> **Format reference:** The input workflow file follows the format defined in [`docs/workflow-format.md`](../../docs/workflow-format.md). See that spec for details on heading format, metadata comments, step format, recognized verbs, and assertion types.

### Step 1: Locate the Workflow File

Use Glob to search for the workflow file:

```
Glob patterns:
  - workflows/multi-user-workflows.md
  - workflows/concurrent-workflows.md
  - workflows/collaboration-workflows.md
```

If no file is found, stop and inform the user:

```
No multi-user workflow file found at /workflows/multi-user-workflows.md.
Please run "generate multi-user workflows" first, or provide the path
to your workflow file.
```

### Step 2: Read and Parse

Read the entire workflow file. For each workflow, extract:

1. **Workflow number** -- from the `## Workflow [N]:` heading
2. **Workflow name** -- the descriptive name after the number
3. **Auth requirement** -- from `<!-- auth: required -->` or `<!-- auth: no -->`
4. **Priority** -- from `<!-- priority: core -->`, `<!-- priority: feature -->`, or `<!-- priority: edge -->`
5. **Personas** -- from `<!-- personas: Admin, Host, Guest1 -->` (comma-separated list)
6. **Estimated steps** -- from `<!-- estimated-steps: N -->`
7. **Sync points** -- from `<!-- sync-points: N -->`
8. **Deprecated flag** -- from `<!-- deprecated: true -->` (skip deprecated workflows)
9. **Preconditions** -- the bullet list under `**Preconditions:**`
10. **Steps** -- each numbered step with its `[PersonaName]` tag and verification sub-steps
11. **Postconditions** -- the bullet list under `**Postconditions:**`

### Step 3: Parse the Persona Registry

Near the top of the workflow file, extract the Persona Registry table and build a Persona Map. For each persona, derive:

- `contextVar`: lowercased persona name + `Ctx` (e.g., `adminCtx`, `guest1Ctx`)
- `pageVar`: lowercased persona name + `Page` (e.g., `adminPage`, `guest1Page`)
- `authFile`: `playwright/.auth/<lowercase-persona>.json`
- `setupFile`: `<lowercase-persona>.setup.ts`
- `emailVar` / `passwordVar`: from the `Credential Env Vars` column (e.g., `ADMIN_EMAIL` / `ADMIN_PASSWORD`)

### Step 4: Build Internal Representation

Organize workflows into a structured list. Each workflow entry includes: number, name, auth flag, priority, personas list, steps (each with a `persona` field, `action`, `verify`, optional `syncVerify` boolean, and `syncTimeout` in ms), preconditions, and postconditions.

Each step's `persona` field is extracted from the `[PersonaName]` tag prefix (e.g., `[Admin]` -> `persona: "Admin"`).

Skip any workflow marked `<!-- deprecated: true -->`. Log skipped workflows to the user:

```
Parsed 20 workflows from multi-user-workflows.md.
Skipped 1 deprecated workflow: #9 (Legacy Shared Calendar).
Converting 19 active workflows.
Personas found: Admin, Host, Guest1, Guest2, Guest3, Viewer (6 total).
```

### Step 5: Create Tasks

Create the main task `"Convert: Multi-User Workflows to Playwright"` (in_progress) with metadata for source file, workflow counts, persona list, and output path. Create the parse task `"Parse: multi-user-workflows.md"` (completed) with metadata for workflow counts by priority, persona count, and sync point total.

---

## Phase 2: Check Existing Project

Before generating, check whether an `e2e/multi-user/` directory already exists.

### Step 1: Check for Existing Files

Use Glob to check for existing project files:

```
Glob patterns:
  - e2e/multi-user/playwright.config.ts
  - e2e/multi-user/package.json
  - e2e/multi-user/tests/*.spec.ts
  - e2e/multi-user/tests/*.setup.ts
```

### Step 2: Determine Strategy

**If no existing project is found:**
- Proceed with fresh generation.
- No further decisions needed.

**If an existing project is found:**
- Read the existing `tests/workflows.spec.ts` to understand what is already covered.
- Read existing `tests/*.setup.ts` files to identify current persona setup files.
- Use `AskUserQuestion` to determine the user's intent:

```
I found an existing Playwright project at e2e/multi-user/ with [N] existing
test blocks and [M] persona setup files.

How would you like to proceed?

1. **Overwrite** -- Replace all generated files with fresh output
2. **Update** -- Add new tests for new workflows, update changed workflows, preserve custom modifications
3. **Cancel** -- Stop and keep existing files unchanged
```

### Step 3: Create the Check Task

Create `"Check: Existing e2e/multi-user/ project"` (completed) with metadata for existing project status, test count, persona setup file count, and chosen strategy.

---

## Phase 3: Selector Discovery [DELEGATE TO AGEN