Persona Create

---
name: persona-create
description: This skill should be used when the user asks to "create a persona", "add a new persona", "set up a new agent role", "add a woterclip persona", or runs the /persona-create command. Interactively creates a new WoterClip persona with SOUL.md, TOOLS.md, and config.yaml.
version: 0.1.0
---

# Create Persona

Interactively create a new WoterClip persona for this repository.

## Prerequisites

Verify `.woterclip/config.yaml` exists. If not, instruct the user to run `/woterclip-init` first.

## Procedure

### Step 1: Gather Persona Details

Ask the user for:

1. **Name** — Display name (e.g., "QA Engineer", "Infra Engineer", "Research Analyst")
2. **Role** — Role type: `engineer`, `orchestrator`, `analyst`, or custom
3. **Label** — GitHub label for routing issues to this persona (e.g., `qa`, `infra`, `research`). Must be unique across existing personas.
4. **Escalates to** — Which persona to escalate to (default: `ceo`)
5. **Model** — Runtime model: `opus`, `sonnet`, or `haiku` (suggest based on role complexity)
6. **Required tools** — Beyond `gh`, which tools does this persona need? Executables (e.g., `docker`) are verified with `command -v`; MCP tool prefixes (e.g., `mcp__neon`, `mcp__plugin_playwright_playwright`) are verified by in-session tool availability — the heartbeat's tool-validation step handles each kind differently, so list them exactly as named here.

### Step 2: Generate SOUL.md

Create a SOUL.md tailored to the persona's role. Use the structure from existing persona templates:

- **Identity** — One-sentence role description
- **Technical Posture** — 5-7 principles for how this persona approaches work
- **Voice and Tone** — Communication style
- **Working Style** — How to approach tasks
- **Boundaries** — What this persona does NOT do (reference other personas)
- **Quality Checklist** — Pre-completion checks

Present the generated SOUL.md to the user for review. Ask if they want to edit any section.

### Step 3: Generate TOOLS.md

Create a TOOLS.md listing:
- Required tools (from step 1)
- Common usage patterns for this persona's role
- Optional tools the user might add later

### Step 4: Generate config.yaml

Create the persona's runtime config:

```yaml
name: <Name>
role: <role>
label: <label>
escalates_to: <escalates_to>

required_tools:
  - gh
  # additional tools from step 1

runtime:
  model: <model>
  thinking_effort: <high for opus, medium for sonnet/haiku>
  max_turns: <300 for opus, 200 for sonnet, 100 for haiku>
  enable_chrome: false
  timeout: 0
  extra_args: []
```

### Step 5: Write Files

1. Create `.woterclip/personas/<label>/` directory
2. Write `SOUL.md`, `TOOLS.md`, `config.yaml`

### Step 6: Update Config

Read `.woterclip/config.yaml` and add the new persona to the `personas` map:

```yaml
<label>:
  path: "personas/<label>"
  label: "<label>"
```

### Step 7: Create GitHub Label

Check whether the label exists with `gh label list --repo <owner/name from config github.repo> --limit 200`. If not, create it: `gh label create <label> --repo <owner/name> --color <hex> --description "WoterClip persona label"`.

### Step 8: Summary

```
Persona created: <Name>
  Label:    <label>
  Model:    <model>
  Escalates: <escalates_to>
  Path:     .woterclip/personas/<label>/

Files:
  ✓ SOUL.md
  ✓ TOOLS.md
  ✓ config.yaml

GitHub label "<label>" created on <owner/name>.

Customize SOUL.md to match your project's specific needs.
```