settings

What this skill does

# Settings

Interactive dashboard for viewing and editing all feature-flow configuration values stored in `.feature-flow.yml`.

**Announce at start:** "Opening feature-flow settings..."

## When to Use

- When the user wants to view or change any feature-flow configuration
- When `.feature-flow.yml` exists and the user wants to explore what's configured
- When the user mentions a specific setting by name (notifications, YOLO, default branch, etc.)
- When the user wants to reset or review design preferences

## Advisor Sub-Actions

If invoked with args `advisor` or `advisor dismiss`, handle as a direct command — do not show the dashboard.

**`feature-flow:settings advisor`** (no further args, or args == `advisor`):

Print the following block verbatim (substituting actual paths):

```
Advisor Beta Header — feature-flow integration

The Claude advisor tool (beta) provides automatic per-turn second-opinion checks on
complex tasks. To enable it, add the beta header to your Claude Code settings.json.

Settings file location:
  macOS:  ~/.claude/settings.json
  Linux:  ${XDG_CONFIG_HOME:-~/.config}/claude/settings.json
  Windows: %APPDATA%\claude\settings.json

Add this to your settings.json under the "env" key:
  {
    "env": {
      "ANTHROPIC_BETA": "advisor-tool-2026-03-01"
    }
  }

If you already have other ANTHROPIC_BETA values, append with a comma:
  "ANTHROPIC_BETA": "other-header,advisor-tool-2026-03-01"

For full details, see docs/advisor.md in the feature-flow plugin source.

To stop the daily tip: feature-flow:settings advisor dismiss
```

Exit the skill after printing. Do not show the settings dashboard.

---

**`feature-flow:settings advisor dismiss`**:

1. Read `.feature-flow.yml`. If it does not exist, create it with default content (same as Step 1 default).
2. Set `hints.advisor.dismissed: true` in the YAML. If a `hints:` block exists, add `advisor: {dismissed: true}` under it. If the block does not exist, append:
   ```yaml
   hints:
     advisor:
       dismissed: true
   ```
3. Write the updated file using the Edit tool (or Write tool if Edit fails).
4. Print: `"Advisor hint dismissed. The daily tip will no longer appear. Re-enable with: feature-flow:settings advisor (then re-add the header)."`

Exit the skill after the confirmation. Do not show the settings dashboard.

---

## Process

### Step 1: Load Configuration

Read `.feature-flow.yml` from the project root.

**If the file does not exist**, create it with these defaults:

```yaml
plugin_version: 1.0.0
notifications:
  on_stop: bell
tool_selector:
  enabled: true
  confidence_threshold: 0.7
  auto_launch_gsd: false
```

Then announce: "Created `.feature-flow.yml` with defaults. You can now configure your settings."

**If the file exists**, read it and parse the current values for all 10 settings.

### Step 2: Display Dashboard

Print the settings dashboard. Use `plugin_version` from the file for the version header. If `plugin_version` is missing, display `unknown`.

```
feature-flow v[plugin_version] — Settings

  Workflow
  ─────────────────────────────────────────
  YOLO stops          [yolo.stop_after values, comma-separated, or "none"]
  Notifications       [notifications.on_stop, or "bell" if unset]
  Default branch      [default_branch, or "auto-detect"]
  Git strategy        [git_strategy, or "merge"]

  Design
  ─────────────────────────────────────────
  Design preferences  [count of defined prefs, e.g. "3 of 5 set" or "not set"]
  Standards           [standards file count and status, e.g. "2 files, enabled" or "disabled" or "not configured"]

  Advanced
  ─────────────────────────────────────────
  Tool selector       [enabled/disabled, threshold, auto-launch]
  Context7 libraries  [count of mappings, e.g. "2 libraries" or "none"]
  CI timeout          [ci_timeout_seconds]s, or "600s (default)"
  KB limits           [knowledge_base.max_lines lines / knowledge_base.stale_days day retention, or defaults]

  Plugins
  ─────────────────────────────────────────
  Registry            [N plugins: M base, K discovered, or "not scanned"]
  Overrides           [count of overrides, or "none"]
```

For multi-value settings, display a summary on one line (e.g., `"brainstorming, plan"` for YOLO stops, `"enabled / 0.70 threshold / manual launch"` for tool selector).

### Step 3: Category Selection

Ask which category the user wants to edit:

```
AskUserQuestion: "Which category would you like to edit?"
Options:
- "Workflow" with description: "YOLO stops, notifications, default branch, git strategy"
- "Design" with description: "Design preferences for code style, testing, UI patterns"
- "Advanced" with description: "Tool selector, Context7 libraries, CI timeout, KB limits"
- "Plugins" with description: "View, rescan, override, or exclude plugins"
- "Done" with description: "Exit settings"
```

If the user selects **Done**, print: "Settings closed." and exit the skill.

Otherwise, continue to Step 4 for the selected category.

### Step 4: Setting Selection Within Category

Based on the selected category, ask which setting to edit.

#### Workflow Category

```
AskUserQuestion: "Which Workflow setting?"
Options:
- "YOLO stops" with description: "Phases where feature-flow pauses for confirmation (currently: [current value])"
- "Notifications" with description: "Alert style when a phase completes (currently: [current value])"
- "Branch & strategy" with description: "Default branch name and git merge/rebase strategy (currently: [branch] / [strategy])"
- "Back" with description: "Return to category selection"
```

#### Design Category

```
AskUserQuestion: "Which Design setting?"
Options:
- "Design preferences" with description: "Edit or reset the 5 code-style preferences (currently: [N] of 5 set)"
- "Standards" with description: "Standards files for design cross-checks (currently: [N files, enabled/disabled/not configured])"
- "Back" with description: "Return to category selection"
```

#### Advanced Category

```
AskUserQuestion: "Which Advanced setting?"
Options:
- "Tool selector" with description: "Intelligent GSD vs feature-flow recommendation (currently: [enabled/disabled])"
- "Context7 libraries" with description: "Documentation library mappings (currently: [N] libraries)"
- "Timeouts & limits" with description: "CI timeout and knowledge base retention limits"
- "Back" with description: "Return to category selection"
```

If the user selects **Back** in any category, return to Step 3.

### Step 5: Edit UI for Each Setting

After the user selects a setting, display its edit UI. On save, write the change to `.feature-flow.yml` using the Edit tool, print a confirmation, then loop back to Step 3 (category selection).

---

#### 5A: YOLO Stops (`yolo.stop_after`)

Display the current stops (empty list = never stop = full YOLO mode).

```
AskUserQuestion (multiSelect: true): "Which phases should YOLO pause after for review? (select all that apply)"
Options:
- "brainstorming" with description: "Pause after brainstorming completes — review design decisions"
- "design" with description: "Pause after design document is written — review the design"
- "verification" with description: "Pause after design verification runs — review blockers/warnings"
- "plan" with description: "Pause after implementation plan is created — review task breakdown"
```

If the user selects phases, present a second `AskUserQuestion` (multiSelect: true) for the remaining 2 phases:

```
AskUserQuestion (multiSelect: true): "Also pause at these later phases?"
Options:
- "implementation" with description: "Pause before subagents start coding — last chance to review"
- "pr" with description: "Pause before pushing and creating the PR — review final diff"
```

Write the combined selections to `yolo.stop_after` as a YAML list. If no phases selected in either question, write an empty list `[]`.

**Confirmation:** `"YOLO stops updated: [selected phases, comma-separated, or 'none (full YOLO)']"`

---

#### 5B: Notifications (`no