runCmd.Flags().StringArrayP("raw-field", "F", []string{}, "Add a string parameter in key=value format (can be used multiple times)")
```

**Issue**: The `--raw-field` flag is registered with the short form `-F` (uppercase), but the example in the Long description uses `-f` (lowercase). Since the `new` command already uses `-f` for `--force`, users copying the example will get an error like `unknown shorthand flag: 'f' in -f`.

**Suggested Fix**: Change the example on line 360 to use `-F`:
```
gh aw run daily-perf-improver -F name=value -F env=prod  # Pass workflow inputs
```

---

#### 2. `mcp add` `--registry` Flag Description Shows Wrong Default URL

**Commands Affected**: `mcp add`
**Priority**: Medium
**Type**: Inaccurate flag description

**Current Output** (`pkg/cli/mcp_add.go` line 362):
```
--registry   MCP registry URL (default: https://api.mcp.github.com/v0)

const DefaultMCPRegistryURL URL = "https://api.mcp.github.com/v0.1"

cmd.Flags().StringVar(&registryURL, "registry", "", "MCP registry URL (default: https://api.mcp.github.com/v0.1)")
```

---

#### 3. `--repo` Flag Description Inconsistency Across Commands

**Commands Affected**: `status`, `enable`, `disable`, `run`
**Priority**: Low
**Type**: Inconsistency between standard helper and inline definitions

**Current Output**:

- `flags.go` helper (used by `pr transfer`, `list`, etc.):
  ```
  -r, --repo   Target repository ([HOST/]owner/repo format). Defaults to current repository
  ```

- `status`, `enable`, `disable`, `run` commands (defined inline in `status.go` and `main.go`):
  ```
  -r, --repo   Target repository (owner/repo format). Defaults to current repository
  ```

**Issue**: The `[HOST/]owner/repo` format (which supports GitHub Enterprise Server) is documented in `addRepoFlag()` helper but omitted when the flag is defined inline in `status.go`, `enableCmd`, `disableCmd`, and `runCmd` (4 occurrences). This is inconsistent and misleads GHES users who try to use these commands with GHES.

**Suggested Fix**: Update the 4 inline definitions to use `"[HOST/]owner/repo format"` or refactor them to use `addRepoFlag()`.

---

#### 4. `new` Command Uses Non-Standard Terminology "AI processor settings"

**Commands Affected**: `new`
**Priority**: Low
**Type**: Inconsistent terminology

**Current Output** (`cmd/gh-aw/main.go` line 114):
```
- AI processor settings
```

**Issue**: The `new` command's `Long` description lists content created by the template as including "AI processor settings". The rest of the codebase consistently uses "engine" (not "processor") for the AI component — `--engine` flag, `Short: "Override AI engine"`, docs use "engine". This one-off term is inconsistent.

**Suggested Fix**: Change "AI processor settings" to "AI engine settings":
```
- AI engine settings
```

---

#### 5. `project new` Example Has Inconsistent Indentation

**Commands Affected**: `project new`
**Priority**: Low
**Type**: Visual inconsistency in help text

**Current Output** (`pkg/cli/project_command.go`):
```
Examples:
  gh aw project new "My Project" --owner `@me`                           # Create user project
  gh aw project new "Team Board" --owner myorg                         # Create org project  
  gh aw project new "Bugs" --owner myorg --link myorg/myrepo           # Create and link to repo
	gh aw project new "Project Q1" --owner myorg --with-project-setup     # With project setup

  gh aw project new "Project Q1" --owner myorg --with-project-setup     # With project setup