swe-feature-onboard

## ⚠️ WORKFLOW INITIALIZATION

**If starting a new session**, first read workflow initialization:
```
mcp__plugin_swe_serena__read_memory("WF_INIT")
```
Follow WF_INIT instructions before executing this skill.

---

# /swe-feature-onboard [KEY] [--quick]

Interactive wizard for registering features in the workflow system.

## Usage

```bash
/swe-feature-onboard              # Full interactive wizard
/swe-feature-onboard MYAPP        # Start with key pre-filled
/swe-feature-onboard MYAPP --quick # Quick mode (30 sec, minimal)
```

## Quick Mode vs Full Mode

| Aspect | Quick Mode | Full Mode |
|--------|------------|-----------|
| Time | ~30 sec | 2-5 min |
| Swarm analysis | No | Optional (10 agents) |
| DOM_* memories | No | Yes (if domains found) |
| SYS_* memories | No | Yes (if systems found) |
| Layer detection | Basic | Detailed |
| Best for | Small features, prototyping | Large codebases |

---

## Stage 1: Basic Info

Ask the user (skip if provided via args):

```
What feature are you onboarding?

1. **Feature Key**: Short identifier used in memory names
   Examples: BACKEND, AUTH, BLOCKS, THEME_DISTRICT

2. **Feature Name**: Human-readable name
   Examples: "Backend API", "Authentication Module"

3. **Root Path(s)**: Where is the code?
   Examples: "src/", "wp-content/themes/district/"
```

**Validation:**
- Key: UPPERCASE, underscores allowed, 2-20 chars
- Path: Must exist in project

---

## Stage 2: Tech Stack

```
What technology does this feature use?

1. **Type**: web_app | library | api | cli | cms | wordpress_theme | wordpress_plugin
2. **Primary Language**: php | typescript | python | go | rust | etc.
3. **Framework** (optional): react | nextjs | laravel | django | wordpress | etc.
```

**Auto-detection:** Scan root path for:
- `package.json` → Node/TypeScript
- `composer.json` → PHP
- `Cargo.toml` → Rust
- `go.mod` → Go
- `style.css` with `Theme Name:` → WordPress theme

---

## Stage 3: Analysis Mode

**Skip in quick mode** - go directly to Stage