viepilot 2.23.0 → 2.45.2

package/bin/vp-tools.cjs

@@ -1137,6 +1137,157 @@ ${colors.cyan}Examples:${colors.reset}
     process.exit(1);
   },
 
+  /**
+   * Output global skill registry as JSON (BUG-016 fix — shell-executable alternative to loadRegistry())
+   */
+  'get-registry': (args) => {
+    const { loadRegistry } = require('../lib/skill-registry.cjs');
+    const registry = loadRegistry();
+    if (!registry) {
+      process.stdout.write('null\n');
+      process.exit(0);
+    }
+    const idFilter = args[0] === '--id' ? args[1] : null;
+    if (idFilter) {
+      const skill = (registry.skills || []).find(s => s.id === idFilter) || null;
+      process.stdout.write(JSON.stringify(skill) + '\n');
+    } else {
+      process.stdout.write(JSON.stringify(registry) + '\n');
+    }
+    process.exit(0);
+  },
+
+  /**
+   * ENH-072: Check npm registry for newer ViePilot version (24h cached).
+   * --silent  exit 0 if up-to-date (no output); exit 1 + print latest if update available
+   * --json    print { installed, latest, has_update }; always exit 0
+   * --force   bypass 24h cache
+   */
+  'check-update': (args) => {
+    const silent = args.includes('--silent');
+    const json = args.includes('--json');
+    const force = args.includes('--force');
+    const { checkLatestVersion } = require('../lib/viepilot-update.cjs');
+
+    checkLatestVersion({ force })
+      .then(({ upToDate, installed, latest }) => {
+        const has_update = !upToDate;
+        if (json) {
+          process.stdout.write(JSON.stringify({ installed, latest, has_update }) + '\n');
+          process.exit(0);
+        }
+        if (silent) {
+          if (has_update) {
+            process.stdout.write(latest + '\n');
+            process.exit(1);
+          } else {
+            process.exit(0);
+          }
+        }
+        // default human-readable output
+        if (has_update) {
+          process.stdout.write(
+            `\n┌──────────────────────────────────────────────────────────────────┐\n` +
+            `│ ✨ ViePilot v${latest} available  (installed: v${installed})`.padEnd(69) + '│\n' +
+            `│    npm i -g viepilot && vp-tools install`.padEnd(69) + '│\n' +
+            `└──────────────────────────────────────────────────────────────────┘\n`
+          );
+          process.exit(1);
+        } else {
+          process.stdout.write(`ViePilot ${installed} is up to date.\n`);
+          process.exit(0);
+        }
+      })
+      .catch(() => {
+        process.exit(0);
+      });
+  },
+
+  /**
+   * ENH-073: Manage cross-project personas.
+   * persona get            → print active persona JSON
+   * persona infer [dir]    → run inferPersona, print result, update context-map
+   * persona list           → list all ~/.viepilot/personas/*.json
+   * persona set <name>     → set active persona by name
+   * persona auto-switch    → auto-detect and switch for cwd (called at skill start)
+   * persona context [dir]  → print persona-context.md content
+   */
+  'persona': (args) => {
+    const {
+      inferPersona, resolvePersona, generatePersonaContext,
+      readActivePersona, writePersona, setActivePersona, listPersonas,
+      updateContextMap, autoSwitch,
+    } = require('../lib/viepilot-persona.cjs');
+
+    const op = args[0] || 'get';
+    const dir = args[1] ? require('path').resolve(args[1]) : process.cwd();
+
+    if (op === 'get') {
+      const persona = readActivePersona();
+      if (!persona) { process.stdout.write('No active persona\n'); process.exit(0); }
+      process.stdout.write(JSON.stringify(persona, null, 2) + '\n');
+      process.exit(0);
+    }
+
+    if (op === 'list') {
+      const personas = listPersonas();
+      if (!personas.length) { process.stdout.write('No personas saved\n'); process.exit(0); }
+      for (const p of personas) {
+        const marker = p.active ? '[active] ' : '         ';
+        process.stdout.write(`${marker}${p.name}  domain:${p.domain}  confidence:${p.confidence}\n`);
+      }
+      process.exit(0);
+    }
+
+    if (op === 'set') {
+      const name = args[1];
+      if (!name) { process.stderr.write('Usage: persona set <name>\n'); process.exit(1); }
+      setActivePersona(name);
+      process.stdout.write(`Active persona set to: ${name}\n`);
+      process.exit(0);
+    }
+
+    if (op === 'infer') {
+      inferPersona(dir).then(persona => {
+        writePersona(persona.name, persona);
+        setActivePersona(persona.name);
+        updateContextMap(dir, persona.name);
+        process.stdout.write(JSON.stringify(persona, null, 2) + '\n');
+        process.exit(0);
+      }).catch(() => process.exit(0));
+      return;
+    }
+
+    if (op === 'auto-switch') {
+      autoSwitch(dir).then(() => process.exit(0)).catch(() => process.exit(0));
+      return;
+    }
+
+    if (op === 'context') {
+      (async () => {
+        let persona = resolvePersona(dir);
+        if (!persona) persona = await inferPersona(dir);
+        process.stdout.write(generatePersonaContext(persona) + '\n');
+        process.exit(0);
+      })().catch(() => process.exit(0));
+      return;
+    }
+
+    process.stderr.write(`Unknown persona op: ${op}\nUsage: persona get|infer|list|set|auto-switch|context\n`);
+    process.exit(1);
+  },
+
+  /**
+   * Scan installed skills and rebuild ~/.viepilot/skill-registry.json (BUG-019)
+   */
+  'scan-skills': (_args) => {
+    const { scanSkills } = require('../lib/skill-registry.cjs');
+    const result = scanSkills();
+    const count = (result && result.skills) ? result.skills.length : 0;
+    process.stdout.write(`✔ Scanned ${count} skill${count !== 1 ? 's' : ''} → ~/.viepilot/skill-registry.json\n`);
+    process.exit(0);
+  },
+
   /**
    * Help
    */
@@ -1224,6 +1375,55 @@ ${colors.cyan}Examples:${colors.reset}
         options: ['--json: Machine-readable JSON output'],
         examples: ['vp-tools info', 'vp-tools info --json'],
       },
+      'get-registry': {
+        usage: 'vp-tools get-registry [--id <skill-id>]',
+        description: 'Output global skill registry as JSON (enables workflow shell integration)',
+        options: ['--id <id>: Output only the matching skill object (null if not found)'],
+        examples: [
+          'vp-tools get-registry',
+          'vp-tools get-registry --id frontend-design',
+        ],
+      },
+      'scan-skills': {
+        usage: 'vp-tools scan-skills',
+        description: 'Scan installed skills and rebuild ~/.viepilot/skill-registry.json',
+        options: [],
+        examples: ['vp-tools scan-skills'],
+      },
+      'check-update': {
+        usage: 'vp-tools check-update [--silent] [--json] [--force]',
+        description: 'Check for latest ViePilot version on npm registry (24h cached)',
+        options: [
+          '--silent  Exit 0 if up-to-date (no output); exit 1 + print latest if update available',
+          '--json    Print { installed, latest, has_update }; always exit 0',
+          '--force   Bypass 24h cache and check now',
+        ],
+        examples: [
+          'vp-tools check-update --silent',
+          'vp-tools check-update --json',
+          'vp-tools check-update --force',
+        ],
+      },
+      'persona': {
+        usage: 'vp-tools persona <op> [dir]',
+        description: 'Manage cross-project personas (ENH-073)',
+        options: [
+          'get          Show active persona JSON',
+          'infer [dir]  Infer persona from project files + git',
+          'list         List all saved personas',
+          'set <name>   Set active persona by name',
+          'auto-switch  Auto-detect and switch persona for current directory',
+          'context [dir] Print persona-context.md content for current project',
+        ],
+        examples: [
+          'vp-tools persona get',
+          'vp-tools persona infer .',
+          'vp-tools persona list',
+          'vp-tools persona set auto-web-saas',
+          'vp-tools persona auto-switch',
+          'vp-tools persona context',
+        ],
+      },
       update: {
         usage: 'vp-tools update [--dry-run] [--yes] [--global]',
         description: 'Update viepilot to npm latest (local dependency, global install, or explicit --global)',
@@ -1282,6 +1482,10 @@ ${colors.cyan}Commands:${colors.reset}
   ${colors.bold}hooks${colors.reset} scaffold|install [--adapter] scaffold: print snippet; install: write to settings.json
   ${colors.bold}config${colors.reset} <get|set|reset>    Read/write language config (~/.viepilot/config.json)
   ${colors.bold}save-state${colors.reset}               Save current state for precise resume
+  ${colors.bold}get-registry${colors.reset} [--id <id>] Output global skill registry as JSON
+  ${colors.bold}scan-skills${colors.reset}               Scan installed skills → ~/.viepilot/skill-registry.json
+  ${colors.bold}check-update${colors.reset} [--silent]   Check for latest ViePilot version on npm (24h cached)
+  ${colors.bold}persona${colors.reset} <op>              Manage user personas (get|infer|list|set|auto-switch|context)
   ${colors.bold}help${colors.reset} [command]           Show help (optionally for specific command)
 
 ${colors.cyan}Examples:${colors.reset}

package/docs/brainstorm/session-2026-04-20.md

@@ -0,0 +1,261 @@
+# Brainstorm Session — 2026-04-20
+
+## Topic
+**ViePilot Skill Registry System** — Third-party skill installation + scan-skills command + workflow skill integration (brainstorm / crystallize / vp-auto gates)
+
+## Status
+In Progress
+
+---
+
+## Problem Statement
+
+ViePilot hiện tại chỉ dùng built-in `vp-*` skills. Khi user muốn xây dựng UI-Direction phức tạp hơn (ví dụ dùng design system cụ thể, component library, hay frontend framework chuyên biệt), không có cơ chế nào để bổ sung context chuyên sâu từ external skills.
+
+Vấn đề cụ thể:
+1. Không có cách cài thêm skills từ bên thứ 3 (npm, GitHub, local)
+2. ViePilot không biết skills nào đang có sẵn trên máy
+3. Workflow (brainstorm / crystallize / vp-auto) không thể tận dụng skill context ngoài vp-* namespace
+4. Quyết định "dùng skill nào" không có điểm lock — vp-auto phải hỏi lại hoặc đoán
+
+---
+
+## Proposed Solution: Skill Registry System
+
+### Core Concept
+
+Ba tầng hoạt động:
+
+```
+[Install]  vp-tools install-skill <source>  → cài skill vào adapter dirs
+[Discover] vp-tools scan-skills             → quét + index toàn bộ skills
+[Apply]    brainstorm → crystallize → auto  → dùng skills theo pipeline
+```
+
+### Tầng 1 — Installation (multi-channel)
+
+`vp-tools install-skill <source>` hỗ trợ:
+
+| Channel | Syntax | Example |
+|---------|--------|---------|
+| npm | `npm:package-name` hoặc bare name | `vp-tools install-skill @vp-skills/frontend-design` |
+| GitHub | `github:org/repo` | `vp-tools install-skill github:myorg/vp-skill-tailwind` |
+| Local | `./path` hoặc absolute path | `vp-tools install-skill ./my-skill` |
+
+Sau khi install → tự động chạy `scan-skills` để cập nhật registry.
+
+Commands bổ sung:
+- `vp-tools uninstall-skill <id>` — xóa khỏi tất cả adapter dirs
+- `vp-tools list-skills` — hiển thị skills đã cài + version + source
+- `vp-tools update-skill <id>` — cập nhật từ source gốc
+
+### Tầng 2 — Scanner & Registry
+
+`vp-tools scan-skills` quét toàn bộ adapter dirs:
+- `~/.claude/skills/` (Claude Code)
+- `~/.cursor/skills/` (Cursor)
+- `~/.codex/skills/` (Codex)
+- `~/.antigravity/skills/` (Antigravity)
+
+Output: `~/.viepilot/skill-registry.json`
+
+```json
+{
+  "version": "1.0",
+  "last_scan": "2026-04-20T10:30:00Z",
+  "scan_paths": ["~/.claude/skills/", "~/.cursor/skills/"],
+  "skills": [
+    {
+      "id": "frontend-design",
+      "name": "Frontend Design",
+      "source": "npm:@vp-skills/frontend-design",
+      "version": "1.2.0",
+      "description": "...",
+      "capabilities": ["ui-generation", "component-design", "responsive-layout"],
+      "tags": ["ui", "design", "frontend", "css", "html"],
+      "best_practices": ["Mobile-first", "Design tokens", "BEM naming"],
+      "adapters": ["claude-code", "cursor"],
+      "installed_paths": {
+        "claude-code": "~/.claude/skills/frontend-design/",
+        "cursor": "~/.cursor/skills/frontend-design/"
+      }
+    }
+  ]
+}
+```
+
+### Tầng 3 — SKILL.md Extended Format
+
+Third-party skills (và vp-* skills nếu muốn) thêm 3 sections mới vào SKILL.md:
+
+```markdown
+## Capabilities
+- ui-generation
+- component-design
+- responsive-layout
+
+## Tags
+ui, design, frontend, css, html, tailwind
+
+## Best Practices
+- Use design tokens for consistency across components
+- Mobile-first: design breakpoints from 320px up
+- BEM naming convention for CSS classes
+```
+
+Scanner đọc các sections này để index. Skills không có sections mới vẫn được scan (fallback: parse description + content tự động).
+
+### Tầng 4 — Workflow Integration Pipeline
+
+#### A. Brainstorm → Silent Skill Application (UI-Direction)
+
+Khi brainstorm có UI signals (keywords: `component`, `design`, `layout`, `screen`, `UI`, v.v.):
+- Load `~/.viepilot/skill-registry.json`
+- Match skills có `capabilities` phù hợp (e.g., `ui-generation`, `component-design`)
+- **Silent apply**: tự động include best practices từ matched skills vào HTML generation
+- Record vào `notes.md`: `## skills_used` section
+
+```yaml
+## skills_used
+- id: frontend-design
+  version: 1.2.0
+  trigger: ui-generation signal
+  applied_at: brainstorm-session
+  best_practices_applied:
+    - Mobile-first
+    - Design tokens
+```
+
+Không hỏi user — chạy ngầm như Background UI Extraction.
+
+#### B. Crystallize → Skill Decision Lock Gate
+
+Bước mới trong `vp-crystallize` (sau scope lock, trước generate SPEC):
+
+1. Đọc `notes.md` → `## skills_used` của session đó
+2. Hiển thị danh sách skills đã/sẽ được dùng
+3. User confirm: required vs optional per phase/task
+4. Ghi vào `PROJECT-CONTEXT.md`:
+
+```markdown
+## Skills
+
+| Skill | Source | Required | Phases | Rationale |
+|-------|--------|----------|--------|-----------|
+| frontend-design | npm:@vp-skills/frontend-design | required | 1, 2 | UI-Direction HTML generation — design token best practices |
+| tailwind-guide | github:org/vp-tailwind | optional | 2 | Phase 2 styling layer |
+```
+
+**Lý do lock ở crystallize:** vp-auto là execution-only — nó đọc SPEC và chạy, không ra quyết định. Tất cả quyết định về "dùng skill nào" phải được lock trước khi vp-auto bắt đầu.
+
+#### C. vp-auto → Silent Skill Execution
+
+vp-auto đọc `## Skills` từ `PROJECT-CONTEXT.md`:
+- Với mỗi task, kiểm tra skills `required` trong phases tương ứng
+- Load best practices từ skill registry
+- Include context vào execution prompt — **không hỏi lại user**
+- Ghi vào task output: `skills_applied: [frontend-design@1.2.0]`
+
+---
+
+## Decisions
+
+| Decision | Options Considered | Chosen | Rationale |
+|----------|--------------------|--------|-----------|
+| Skill source channels | npm-only / all channels | All channels (npm + github + local) | Flexibility cho cả published và WIP skills |
+| Scanner scope | ViePilot-only dirs / all adapter dirs | All adapter dirs | Discover tất cả skills user đã cài qua bất kỳ tool nào |
+| Gate model | Required block / heuristic prompt / silent / hybrid | Silent auto-apply + crystallize-time lock | vp-auto không hỏi lại; quyết định từ crystallize. Nhất quán với ui-direction guard |
+| SKILL.md format | Giữ nguyên / extend / file riêng | Extend — thêm Capabilities/Tags/Best Practices | Backward compat; scanner vẫn parse skills cũ |
+| Lock storage | SPEC.md per-task / PROJECT-CONTEXT.md ## Skills / file riêng | PROJECT-CONTEXT.md ## Skills | Tương tự ## Tech Stack — project-level; dễ đọc cho vp-auto |
+| Phase 1 target | Scanner / Installer / Brainstorm integration | Scanner + registry first | Nền tảng cho mọi tính năng phía sau |
+
+---
+
+## Open Questions
+
+| ID | Question | Priority | Due |
+|----|----------|----------|-----|
+| Q1 | Có cần `vp-tools publish-skill` để user publish skill lên npm không? | low | next milestone |
+| Q2 | Skill versioning: nếu skill update, best practices thay đổi — có cần re-crystallize không? | medium | Phase 4 design |
+| Q3 | Skill conflict: 2 skills có cùng capability, workflow ưu tiên cái nào? | medium | Phase 3 design |
+| Q4 | Có cần một "official ViePilot skills registry" (marketplace) hay chỉ dựa vào npm search? | low | future |
+
+---
+
+## Phases
+
+### Phase 1 — Skill Registry Foundation
+**Goal**: `vp-tools scan-skills` + `~/.viepilot/skill-registry.json` + extended SKILL.md format spec
+
+Tasks:
+1. `lib/skill-registry.cjs` — scanner: traverse adapter dirs, parse SKILL.md (extended + legacy), build JSON
+2. `bin/viepilot.cjs` — add `scan-skills` subcommand + `list-skills` display
+3. `docs/user/features/skill-registry.md` — extended SKILL.md format spec + scanner docs
+4. `tests/unit/vp-skill-registry.test.js` — 15+ contract tests (scan, parse, index, legacy compat)
+
+Target version: **2.26.0**
+
+### Phase 2 — Third-party Skill Installation
+**Goal**: `vp-tools install-skill` (npm + github + local) + `uninstall-skill` + `update-skill`
+
+Tasks:
+1. `lib/skill-installer.cjs` — multi-channel installer (npm exec + git clone + fs copy)
+2. `bin/viepilot.cjs` — add `install-skill`, `uninstall-skill`, `update-skill` subcommands
+3. Post-install hook: auto-run `scan-skills`
+4. `tests/unit/vp-skill-installer.test.js` — 12+ tests (each channel, auto-scan trigger)
+
+Target version: **2.27.0**
+
+### Phase 3 — Brainstorm Integration (UI-Direction silent apply)
+**Goal**: brainstorm.md detects UI signals → loads registry → silently applies matched skill best practices → records `## skills_used` in notes.md
+
+Tasks:
+1. `workflows/brainstorm.md` — add skill registry load step + signal matching logic + silent apply rule
+2. `skills/vp-brainstorm/SKILL.md` — document skill integration behavior
+3. `tests/unit/brainstorm-skill-integration.test.js` — 10+ tests
+
+Target version: **2.28.0**
+
+### Phase 4 — Crystallize Skill Decision Gate
+**Goal**: crystallize.md new step → skill confirmation gate → `## Skills` in PROJECT-CONTEXT.md
+
+Tasks:
+1. `workflows/crystallize.md` — add skill gate step (read notes.md skills_used → AUQ confirm → write PROJECT-CONTEXT.md)
+2. `templates/project/PROJECT-CONTEXT.md` — add `## Skills` section template
+3. `skills/vp-crystallize/SKILL.md` — document skill gate
+4. `tests/unit/crystallize-skill-gate.test.js` — 10+ tests
+
+Target version: **2.29.0**
+
+### Phase 5 — vp-auto Silent Skill Execution
+**Goal**: autonomous.md reads `## Skills` from PROJECT-CONTEXT.md → per-task silent context injection
+
+Tasks:
+1. `workflows/autonomous.md` — add skill context load step + per-task skill injection rule
+2. `skills/vp-auto/SKILL.md` — document silent skill execution
+3. `tests/unit/autonomous-skill-execution.test.js` — 8+ tests
+
+Target version: **2.30.0**
+
+---
+
+## Background UI Extraction
+
+Waiver — session topic is a framework feature (skill registry), not a consumer app UI. No UI Direction artifacts needed.
+
+---
+
+## Project meta intake (FEAT-009)
+
+Waiver — ViePilot framework repo; profile binding already exists.
+
+---
+
+## Session Summary
+
+- **Feature**: ViePilot Skill Registry System
+- **Suggested ID**: FEAT-020
+- **Scope**: 5 phases — registry/scanner → installer → brainstorm integration → crystallize gate → vp-auto execution
+- **Key architectural decision**: Skills are **silent auto-apply** at brainstorm time; **locked at crystallize** time; **executed without re-asking** by vp-auto
+- **Backward compat**: Existing SKILL.md files still work — scanner gracefully handles missing extended sections
+- **First deliverable**: `vp-tools scan-skills` + `~/.viepilot/skill-registry.json` (Phase 1 → v2.26.0)

package/docs/brainstorm/session-2026-04-24.md

@@ -0,0 +1,131 @@
+# Brainstorm Session — 2026-04-24
+
+## Session Info
+- **Date**: 2026-04-24
+- **Topic**: vp-persona — ViePilot Workflow Customization Skill
+- **Status**: Completed
+- **workflow_version**: 2.41.0
+
+## Core Idea
+
+A new skill `/vp-persona` that creates a **user-level, cross-project identity** for ViePilot.
+Lets users customize ALL ViePilot workflows to fit their domain, profession, and interests —
+without re-declaring context per project.
+
+## Problem Statement
+
+ViePilot is currently a general-purpose framework. Multi-domain professionals ("kiêm nhiệm")
+working across Web SaaS, Embedded, Data Science, Mobile face:
+- Brainstorm topics irrelevant to their domain
+- Wrong phase templates
+- No cross-project user identity
+- Must re-declare stack/context for every project
+
+## Key Design Decisions
+
+### 1. Multi-Persona architecture (not single profile)
+- `~/.viepilot/personas/` — named persona files
+- `~/.viepilot/persona.json` — active persona pointer
+- `~/.viepilot/context-map.json` — directory → persona bindings
+
+### 2. Layered resolution (3 layers)
+```
+Priority: project > session > global
+1. .viepilot/persona-override.json   ← per-project explicit
+2. context-map.json pattern match    ← directory-based auto
+3. ~/.viepilot/persona.json (active) ← global default
+```
+
+### 3. Switch + Merge both supported
+- **Switch**: bind project dir to a named persona, change with 1 command
+- **Merge**: create hybrid persona from multiple domains (e.g. IoT Full-stack = web-saas + embedded-iot)
+- Analogy: git branch (switch) + git merge (merge)
+
+### 4. Auto-detection from project files
+| Signal file | Detected domain |
+|------------|-----------------|
+| `package.json` + `prisma/` | web-saas |
+| `CMakeLists.txt` + `sdkconfig` | embedded |
+| `requirements.txt` + `notebooks/` | data-science |
+| `pubspec.yaml` / `*.xcodeproj` | mobile |
+| `Dockerfile` + `terraform/` | devops |
+| `pyproject.toml` + `langchain` | ai-product |
+
+### 5. Persona schema
+```json
+{
+  "name": "Web SaaS Dev",
+  "domain": "web-saas",
+  "role": "full-stack",
+  "stacks": ["nextjs", "nestjs", "postgresql"],
+  "team_size": "solo",
+  "output_style": "lean",
+  "brainstorm": {
+    "topic_priority": ["auth", "user-data", "api", "admin"],
+    "topic_skip": ["embedded", "content-mgmt"]
+  },
+  "phase_template": "lean-startup",
+  "interests": ["ai-integration", "saas", "startup"]
+}
+```
+
+### 6. Domain Packs (5 built-in + community)
+| Pack | Extra topics | Phase template | Extra architect pages |
+|------|-------------|----------------|----------------------|
+| `web-saas` | Billing, Multi-tenant, Onboarding | Auth→Core→Monetize→Scale | billing.html, tenant.html |
+| `data-science` | Dataset mgmt, Model versioning, Drift monitoring | Data→EDA→Train→Serve→Monitor | ml-pipeline.html |
+| `mobile` | Push, Offline sync, Store submit | Auth→Core→Offline→Submit | mobile-flow.html |
+| `devops` | IaC, CI/CD, SLO, Incident | Infra→CI/CD→Observe→Runbooks | infra-topology.html |
+| `ai-product` | LLM integration, RAG, Eval/feedback | Wrapper→Prompt→RAG→Eval→UX | llm-arch.html |
+
+### 7. vp-persona commands
+```
+/vp-persona                      → Show active persona
+/vp-persona --create web-saas    → Create new persona (wizard)
+/vp-persona --switch embedded    → Switch active persona
+/vp-persona --list               → List all personas
+/vp-persona --bind . web-saas    → Bind current dir to persona
+/vp-persona --auto               → Enable auto-detect
+/vp-persona --merge web embedded → Create hybrid persona
+/vp-persona --export / --import  → Backup/share personas
+```
+
+### 8. Workflow adaptations when persona active
+- **vp-brainstorm**: topic order reordered by priority; skipped topics hidden; domain pack topics injected
+- **vp-auto**: stack preflight uses persona stacks automatically; persona-context.md injected per task
+- **vp-crystallize**: output_style "lean" → shorter docs; "enterprise" → full docs + compliance
+- **vp-evolve**: new phase suggestions follow persona's phase_template
+
+## Phases
+
+### Phase 1 — Foundation
+- `vp-persona` skill + wizard (5-question Q&A)
+- `~/.viepilot/personas/` multi-file support
+- `persona-context.md` injection into all skills
+
+### Phase 2 — Multi-context
+- `context-map.json` + directory binding (`--bind`)
+- Auto-detection from project files
+- Session-start smart prompt for multi-domain users
+
+### Phase 3 — Domain Packs
+- 5 built-in domain packs (web-saas, data-science, mobile, devops, ai-product)
+- Domain pack schema + community extensibility (npm install viepilot-domain-*)
+
+### Phase 4 — Merge + Advanced
+- `/vp-persona --merge` hybrid personas
+- Interest-based proactive hints in brainstorm
+- Per-project `persona-override.json`
+
+## Open Questions
+- Should domain packs be separate npm packages or bundled?
+- How to handle conflicts when merge produces duplicate topics?
+- Should `persona-context.md` be injected as a system-prompt prefix or as a workflow step?
+
+## Project meta intake (FEAT-009)
+- Profile binding: skipped (this is ViePilot framework repo itself)
+
+## Background extracted ideas
+- Interest-based proactive suggestions (e.g. "ai-integration" interest → proactive LLM arch hints)
+- Community domain pack registry (viepilot-domain-fintech, viepilot-domain-healthcare...)
+- Persona export/import for team sharing (onboard new dev with same persona)