workflow-setup

# Workflow Setup

## Purpose
Automate the development environment setup for worktree-based workflows. This skill is called by `workflow` during the "start" phase to create an isolated development environment for each ticket.

## When to Use

This skill is **not user-invocable**. It is called internally by the `workflow` skill when:
- Starting work on a new ticket (`/workflow start PROJ-123`)
- Creating an isolated worktree environment for a feature branch

## Quick Reference
- **Setup**: Run during framework wizard via `workflow` skill configure
- **Config**: `.claude/workflow-config.json`
- **Creates**: Git worktree, copies env files, installs deps, opens IDE
- **Requires**: Branch name from workflow
- **Output**: Worktree ready, pending-action.json for session handoff

## Configure Mode

Called during framework setup wizard (via `workflow` skill) to configure worktree preferences:

```
/workflow configure  # Includes workflow-setup configuration
```

**Discovers:**
- Preferred worktree base path
- IDE preference (Cursor, VSCode, WebStorm)
- Environment file copying preference

**Outputs:** `.claude/workflow-config.json`

```json
{
  "worktreeBasePath": "../worktrees/my-project",
  "ide": "Cursor",
  "copyEnvFiles": true
}
```

### Discovery Procedure

1. **Detect project name** from `package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml`, or directory name
2. **Suggest worktree path** based on project name: `../worktrees/<project-name>`
3. **Detect installed IDEs** by checking for `cursor`, `code`, `webstorm` commands
4. **Propose configuration** to user for approval
5. **Save to** `.claude/workflow-config.json`

## What It Does

1. **Creates git worktree** at configured base path
2. **Copies `.env*` files** from source repo
3. **Installs dependencies** via auto-detected setup command
4. **Creates workflow directory** at `.claude/workflow/<branch>/`
5. **Copies plan** if `.claude/plan.md` exists in source
6. **Writes pending-action.json** for session handoff
7. *