viepilot 1.9.11 → 2.1.0

package/skills/vp-brainstorm/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vp-brainstorm
-description: "Brainstorm session để thu thập ý tưởng, quyết định cho dự án"
-version: 0.6.3
+description: "Brainstorm session to collect ideas and decisions for the project"
+version: 1.1.0
 ---
 
 <cursor_skill_adapter>
@@ -10,7 +10,7 @@ version: 0.6.3
 - Treat all user text after the skill mention as `{{VP_ARGS}}`
 
 ## B. User Prompting
-Prompt user conversationally với numbered list options.
+Prompt user conversationally with numbered list options.
 
 ## C. Tool Usage
 Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`, `WebFetch`, `Subagent`
@@ -25,28 +25,39 @@ Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`,
 <implementation_routing_guard>
 ## Implementation routing guard (ENH-021)
 
-- Trong phạm vi **session** (`docs/brainstorm/*`, `.viepilot/ui-direction/*`). **Không** implement thay **`/vp-auto`** cho `lib/`, `tests/`, thay đổi framework `workflows/`/`skills/` — sau brainstorm dùng **`/vp-crystallize`** / **`/vp-evolve`** → **`/vp-auto`** tùy giai đoạn. Override explicit — nêu rõ trong chat.
+- Scoped to **session artifacts** (`docs/brainstorm/*`, `.viepilot/ui-direction/*`). Does **not** implement on behalf of **`/vp-auto`** for `lib/`, `tests/`, or framework `workflows/`/`skills/` changes — after brainstorm use **`/vp-crystallize`** / **`/vp-evolve`** → **`/vp-auto`** depending on the stage. Explicit override — state it in chat.
 </implementation_routing_guard>
 
 
 <objective>
-Thu thập ý tưởng, requirements, quyết định kiến trúc cho dự án thông qua interactive Q&A.
-
-Hỗ trợ:
-- Tạo session mới
-- Tiếp tục session cũ
-- Xem lại session trước đó
-- Landing page layout discovery (hỏi thêm để chốt bố cục)
-- In-session research (research ngay trong phiên brainstorm theo yêu cầu)
-- UI Direction mode: tạo/cập nhật HTML prototype + notes trong `.viepilot/ui-direction/{session-id}/` — hỗ trợ **multi-page** (`pages/{slug}.html` + hub `index.html`) và hook **`## Pages inventory`** trong `notes.md` khi có `pages/` (FEAT-007)
-- **Product horizon (ENH-014):** mọi session phải duy trì **`## Product horizon`** khi thảo luận capability/milestone — tier tags `(MVP)` / `(Post-MVP)` / `(Future)`, non-goals, deferred capabilities; hoặc ghi rõ **single-release / no deferred epics** (contract: `workflows/brainstorm.md`)
-- **Project meta intake (FEAT-009):** sau khi **scope locked**, **trước** `Completed` / `/end`, nếu thiếu `.viepilot/META.md` (`viepilot_profile_id`) — chạy Q&A **tuần tự** có proposal; đọc/ghi `~/.viepilot/profile-map.md`; tạo `~/.viepilot/profiles/<slug>.md` + binding theo **`docs/dev/global-profiles.md`**. Nếu đã có profile bound — skip intake mặc định (hỏi đổi nếu cần).
-- **UX walkthrough (FEAT-010 + ENH-019 + ENH-020):** trong **`--ui`**, lệnh **`/research-ui`** hoặc **`/research ui`** chạy 3 phase — mô phỏng **end-user** (kèm **content stress pass** + **stress recipes theo archetype** → **Stress findings**) → **UX designer + web research** → chỉnh `index.html` / `pages/*.html` / `style.css` và ghi **`## UX walkthrough log`** trong `notes.md` (đồng bộ hub + **Pages inventory** khi multi-page).
+Collect ideas, requirements, and architecture decisions for the project through interactive Q&A.
+
+Supports:
+- Create a new session
+- Continue a previous session
+- Review a past session
+- Landing page layout discovery (follow-up questions to finalize layout)
+- In-session research (research during the brainstorm session on demand)
+- UI Direction mode: create/update HTML prototype + notes under `.viepilot/ui-direction/{session-id}/` — supports **multi-page** (`pages/{slug}.html` + hub `index.html`) and the **`## Pages inventory`** hook in `notes.md` when `pages/` exists (FEAT-007)
+- **Phase assignment (ENH-030):** in every session, features/capabilities are assigned directly to Phase 1, Phase 2, Phase 3... — no MVP/Post-MVP/Future tiers. Session file stores assignments in the `## Phases` section.
+- **Project meta intake (FEAT-009):** after **scope locked**, **before** `Completed` / `/end`, if `.viepilot/META.md` (`viepilot_profile_id`) is missing — run **sequential** Q&A with proposals; read/write `~/.viepilot/profile-map.md`; create `~/.viepilot/profiles/<slug>.md` + binding per **`docs/dev/global-profiles.md`**. If a profile is already bound — skip intake by default (ask if change needed).
+- **UX walkthrough (FEAT-010 + ENH-019 + ENH-020):** in **`--ui`** mode, command **`/research-ui`** or **`/research ui`** runs 3 phases — simulates **end-user** (with **content stress pass** + **stress recipes by archetype** → **Stress findings**) → **UX designer + web research** → update `index.html` / `pages/*.html` / `style.css` and write **`## UX walkthrough log`** in `notes.md` (sync hub + **Pages inventory** for multi-page).
+- **Background UI extraction (ENH-026):** automatically detects UI signal keywords in every brainstorm session (no `--ui` flag required); silent accumulation buffer; surfaces for confirmation when topic ends, `/save`, or ≥5 signals — does not interrupt the main conversation.
+- **Architect Design Mode (FEAT-011):** `/vp-brainstorm --architect` or auto-activate when ≥3 components/services detected; generate HTML workspace (architecture, data-flow, decisions, tech-stack, tech-notes, feature-map) with Mermaid diagrams; incremental update per decision; `/review-arch` command; machine-readable `notes.md` YAML schema.
+- **ERD page (ENH-027):** Architect workspace includes `erd.html` — Mermaid `erDiagram`, entity list table, relationship summary; triggered by DB/entity/table/relationship keywords; notes.md `## erd` YAML section exported to ARCHITECTURE.md `## Database Schema` via crystallize Step 1D.
+- **User Use Cases page (ENH-028):** Architect workspace includes `user-use-cases.html` — actor/use-case diagram (Mermaid flowchart), use case table; triggered by user/role/actor/story keywords; notes.md `## use_cases` YAML section exported to PROJECT-CONTEXT.md `## User Stories & Use Cases` via crystallize Step 1D.
+- **C4Context/Sequence/Deployment/APIs pages (ENH-029, 12-page workspace):** Architect workspace expanded to 12 pages — `sequence-diagram.html` (per-scenario sequenceDiagram), `deployment.html` (infra graph + environments + CI/CD pipeline), `apis.html` (endpoint tables with HTTP method badges); page boundary rules table; trigger keywords for sequence/deploy/API; notes.md `## apis` YAML section; deployment+APIs exported to ARCHITECTURE.md via crystallize Step 1D (sequence excluded — scenario docs are not architecture artifacts).
 
 **Creates/Updates:**
 - `docs/brainstorm/session-{YYYY-MM-DD}.md`
 
 **After:** Ready for `/vp-crystallize`
+
+**Language configuration (ENH-032):**
+- Step 0 reads `~/.viepilot/config.json` → `BRAINSTORM_LANG` = `language.document` (default: `en`).
+- `BRAINSTORM_LANG` is used for brainstorm file storage and generated content.
+- User session language takes precedence over config if different.
+- Configure via: `vp-tools config set language.document vi`
 </objective>
 
 <execution_context>
@@ -55,12 +66,12 @@ Hỗ trợ:
 
 <context>
 Optional flags:
-- `--new` : Force tạo session mới
-- `--continue` : Tiếp tục session gần nhất
-- `--list` : Liệt kê các sessions
-- `--landing` : Ưu tiên flow Landing Page layout discovery
-- `--research` : Bật proactive research suggestions trong phiên
-- `--ui` : Bật UI Direction mode (live HTML/CSS direction artifacts)
+- `--new` : Force create a new session
+- `--continue` : Continue the most recent session
+- `--list` : List all sessions
+- `--landing` : Prioritize the Landing Page layout discovery flow
+- `--research` : Enable proactive research suggestions during the session
+- `--ui` : Enable UI Direction mode (live HTML/CSS direction artifacts)
 </context>
 
 <process>
@@ -70,20 +81,20 @@ Key steps:
 1. Detect existing sessions
 2. Ask user intent (new/continue/review)
 3. Load context if continuing
-4. Run interactive Q&A với topic-based structure
-5. Nếu topic là landing page: hỏi thêm bố cục + tham khảo `21st.dev` để đề xuất section/components
-6. Nếu topic cần UI/UX: tạo/cập nhật UI Direction artifacts trong `.viepilot/ui-direction/{session-id}/` — legacy: `index.html` + `style.css` + `notes.md`; multi-page: thêm `pages/*.html`, `index.html` làm hub, và sau mỗi thay đổi page cập nhật **`## Pages inventory`** trong `notes.md` (xem `docs/user/features/ui-direction.md`)
-6b. Khi user gõ **`/research-ui`** hoặc **`/research ui`** trong phiên UI: làm đúng **`workflows/brainstorm.md`** (FEAT-010) — không gộp vào bước research ngắn thường lệ
-7. Nếu user yêu cầu research hoặc cần làm rõ quyết định: research ngay trong session và quay lại topic
-8. Khi topic thêm/sửa capability hoặc release scope: cập nhật **`## Product horizon`** trong session (merge, không xóa tier tags im lặng) theo `workflows/brainstorm.md`
-9. Trước khi hoàn tất phiên: **bước 5 — Project meta intake (FEAT-009)** trong `workflows/brainstorm.md` khi binding thiếu; sequential Q&A + profile-map disambiguation + ghi global profile + `.viepilot/META.md`
-10. Save session with structured format (bao gồm **`## Project meta intake (FEAT-009)`**, research notes + UI direction references + **Product horizon** khi có)
+4. Run interactive Q&A with topic-based structure
+5. If topic is a landing page: ask follow-up layout questions + reference `21st.dev` to suggest sections/components
+6. If topic needs UI/UX: create/update UI Direction artifacts under `.viepilot/ui-direction/{session-id}/` — legacy: `index.html` + `style.css` + `notes.md`; multi-page: add `pages/*.html`, `index.html` as hub, and after each page change update **`## Pages inventory`** in `notes.md` (see `docs/user/features/ui-direction.md`)
+6b. When user types **`/research-ui`** or **`/research ui`** during a UI session: follow **`workflows/brainstorm.md`** exactly (FEAT-010) — do not merge into the short regular research step
+7. If user requests research or needs to clarify a decision: research inline in the session and return to the topic
+8. When a topic adds/modifies a capability: update **`## Phases`** in the session per `workflows/brainstorm.md`
+9. Before completing the session: **step 5 — Project meta intake (FEAT-009)** in `workflows/brainstorm.md` when binding is missing; sequential Q&A + profile-map disambiguation + write global profile + `.viepilot/META.md`
+10. Save session with structured format (including **`## Project meta intake (FEAT-009)`**, research notes + UI direction references + **`## Phases`**)
 11. Suggest next action: `/vp-crystallize`
 </process>
 
 <success_criteria>
-- [ ] Session file created/updated với đầy đủ sections
-- [ ] Decisions documented với rationale
+- [ ] Session file created/updated with all required sections
+- [ ] Decisions documented with rationale
 - [ ] Open questions listed
 - [ ] Action items captured
 - [ ] Landing page topics include explicit layout selection questions
@@ -91,8 +102,8 @@ Key steps:
 - [ ] Research can be executed inside the same brainstorm session
 - [ ] UI Direction artifacts created/updated when UI mode is active
 - [ ] Multi-page sessions: hub links + `## Pages inventory` stay in sync with `pages/*.html`
-- [ ] **FEAT-010 + ENH-019 + ENH-020**: `/research-ui` (khi `--ui`) chạy đủ 3 phase, gồm **content stress pass** + **archetype recipes** + **`## UX walkthrough log`** (có **Stress findings**) khi có chỉnh prototype
-- [ ] `## Product horizon` present với MVP / Post-MVP / Future (hoặc explicit single-release statement) khi scope được thảo luận
-- [ ] **FEAT-009**: intake hoàn tất hoặc binding đã có **hoặc** waiver có lý do trước Completed; session ghi **`## Project meta intake (FEAT-009)`**
+- [ ] **FEAT-010 + ENH-019 + ENH-020**: `/research-ui` (when `--ui`) runs all 3 phases, including **content stress pass** + **archetype recipes** + **`## UX walkthrough log`** (with **Stress findings**) when prototype is updated
+- [ ] `## Phases` present with Phase 1 having real content when scope is discussed
+- [ ] **FEAT-009**: intake completed, binding already present, **or** waiver with reason before Completed; session records **`## Project meta intake (FEAT-009)`**
 - [ ] Next steps suggested
 </success_criteria>

package/skills/vp-crystallize/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vp-crystallize
-description: "Chuyển đổi brainstorm thành executable artifacts"
-version: 0.5.2
+description: "Convert brainstorm sessions into executable artifacts"
+version: 0.8.0
 ---
 
 <cursor_skill_adapter>
@@ -10,7 +10,7 @@ version: 0.5.2
 - Treat all user text after the skill mention as `{{VP_ARGS}}`
 
 ## B. User Prompting
-Prompt user conversationally với numbered list options.
+Prompt user conversationally with numbered list options.
 
 ## C. Tool Usage
 Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`, `WebFetch`, `Subagent`
@@ -25,23 +25,23 @@ Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`,
 <implementation_routing_guard>
 ## Implementation routing guard (ENH-021)
 
-- Tạo **artifact** trong `.viepilot/` (và template copy) từ brainstorm — **không** thay **`/vp-auto`** để implement mã ứng dụng / framework shipping. Backlog feature code: **`/vp-evolve`** + **`/vp-auto`**. Xem `workflows/request.md`.
+- Creates **artifacts** in `.viepilot/` (and template copy) from brainstorm — does **not** replace **`/vp-auto`** for implementing application code / framework shipping. Backlog feature code: **`/vp-evolve`** + **`/vp-auto`**. See `workflows/request.md`.
 </implementation_routing_guard>
 
 
 <objective>
-Chuyển đổi brainstorm sessions thành structured artifacts để AI có thể autonomous execution.
+Convert brainstorm sessions into structured artifacts for autonomous AI execution.
 
 **Creates:**
 ```
 .viepilot/
-├── AI-GUIDE.md          # Navigation cho AI
-├── PROJECT-META.md      # Metadata dự án
+├── AI-GUIDE.md          # AI navigation guide
+├── PROJECT-META.md      # Project metadata
 ├── ARCHITECTURE.md      # System design
 ├── architecture/        # ENH-022: *.mermaid sidecars (mirror fenced diagrams)
 ├── PROJECT-CONTEXT.md   # Domain knowledge + `<product_vision>` (phased scope)
 ├── SYSTEM-RULES.md      # Coding rules & standards
-├── ROADMAP.md           # MVP phases & tasks + **Post-MVP / Product horizon** block (mandatory)
+├── ROADMAP.md           # Phases & tasks in order from phases_inventory
 ├── TRACKER.md           # Progress tracking
 ├── HANDOFF.json         # Machine-readable state
 └── schemas/             # Database, API, Kafka schemas
@@ -55,7 +55,7 @@ Chuyển đổi brainstorm sessions thành structured artifacts để AI có th
 - Updated `README.md`
 
 **ViePilot profile (FEAT-009):**
-- Đọc `.viepilot/META.md` → file `~/.viepilot/profiles/<slug>.md` (contract: `docs/dev/global-profiles.md`); pre-fill Step 0; merge vào **ARCHITECTURE** (`## ViePilot organization context`), **PROJECT-CONTEXT** (`## ViePilot active profile`), **AI-GUIDE** quick context.
+- Reads `.viepilot/META.md` → file `~/.viepilot/profiles/<slug>.md` (contract: `docs/dev/global-profiles.md`); pre-fills Step 0; merges into **ARCHITECTURE** (`## ViePilot organization context`), **PROJECT-CONTEXT** (`## ViePilot active profile`), **AI-GUIDE** quick context.
 
 **Stack intelligence (global cache):**
 - `~/.viepilot/stacks/{stack}/SUMMARY.md`
@@ -65,6 +65,18 @@ Chuyển đổi brainstorm sessions thành structured artifacts để AI có th
 - `.viepilot/STACKS.md` (project-local index to global cache)
 
 **After:** Ready for `/vp-auto`
+
+**UI direction hard gate (ENH-026):**
+- Step 1A scans brainstorm for UI signal keywords; if ≥3 signals detected + no artifacts → **STOP** with 2-option dialogue (go back to brainstorm --ui OR proceed with assumptions written to ARCHITECTURE.md). Enforces direction-first workflow before crystallize proceeds.
+
+**Architect artifacts consumption (FEAT-011):**
+- Step 1D reads `.viepilot/architect/{session}/notes.md` YAML — imports `decisions[]` → ARCHITECTURE.md, uses `tech_stack{}` as authoritative stack (conflict → ask user), surfaces `open_questions[]` with `status: open`. Soft suggestion (not hard block) when architect dir missing but ≥5 services detected.
+
+**Language configuration (ENH-032):**
+- Step 0-A reads `~/.viepilot/config.json` → `DOCUMENT_LANG` (default: `en`) and `COMMUNICATION_LANG` (default: `en`).
+- `DOCUMENT_LANG` controls content language for all generated files (ROADMAP, TRACKER, ARCHITECTURE, etc.).
+- `COMMUNICATION_LANG` controls prompt/confirmation language for this session.
+- Configure via: `vp-tools config set language.document vi`
 </objective>
 
 <execution_context>
@@ -78,8 +90,8 @@ Execute workflow from `@$HOME/.cursor/viepilot/workflows/crystallize.md`
 Key steps:
 
 ### Step 0: Collect Project Metadata
-- **FEAT-009:** Load `.viepilot/META.md` + global profile file first (`workflows/crystallize.md`); set `profile_resolved` or `none`; pre-fill org/website khi có profile.
-Ask user for (confirm proposals từ profile nếu có):
+- **FEAT-009:** Load `.viepilot/META.md` + global profile file first (`workflows/crystallize.md`); set `profile_resolved` or `none`; pre-fill org/website when profile is present.
+Ask user for (confirm proposals from profile if present):
 - Project name, description
 - Organization name, website
 - Package Base ID (e.g., com.company.project)
@@ -93,8 +105,8 @@ Ask user for (confirm proposals từ profile nếu có):
 - Load all brainstorm sessions
 - Extract: decisions, architecture, schemas, features
 - Extract selected tech stacks
-- **Product horizon (ENH-014):** parse each session **`## Product horizon`**; build consolidated **horizon inventory**; record **single-release** mode when stated; run **validation gate** (missing section vs multi-release discussion → stop and ask; tier conflicts → stop) — full contract: `workflows/crystallize.md` Step 1
-- Validate completeness (tech stack, features, schema/API clarity, **horizon gate**)
+- **Phase assignment (ENH-030):** parse `## Phases` from brainstorm sessions; build `phases_inventory`; run phase assignment gate (all features must have a phase — full contract: `workflows/crystallize.md` Step 1)
+- Validate completeness (tech stack, features, schema/API clarity, **phase assignment gate**)
 
 ### Step 1A: Consume UI direction (if present)
 - Read `.viepilot/ui-direction/{session-id}/notes.md` first, then `style.css`, then HTML:
@@ -121,7 +133,7 @@ Ask user for (confirm proposals từ profile nếu có):
 - Quick lookup table
 - Context loading strategy
 - File relationships
-- **FEAT-009:** Quick context cho `profile_id` + path profile khi đã resolve
+- **FEAT-009:** Quick context for `profile_id` + profile path when resolved
 
 ### Step 3: Generate PROJECT-META.md
 - Project info
@@ -129,11 +141,11 @@ Ask user for (confirm proposals từ profile nếu có):
 - Package structure
 - Developer info
 - File headers template
-- **FEAT-009:** Align Organization với profile đã confirm (public only)
+- **FEAT-009:** Align Organization with confirmed profile content (public only)
 
 ### Step 4: Generate ARCHITECTURE.md
 - System overview
-- **FEAT-009:** Section `## ViePilot organization context` khi có profile (hoặc dòng none)
+- **FEAT-009:** Section `## ViePilot organization context` when profile is present (or none line)
 - Services definitions
 - Data flow
 - Technology decisions
@@ -147,12 +159,12 @@ Ask user for (confirm proposals từ profile nếu có):
 - **ENH-022:** For each diagram type with real Mermaid, write **`.viepilot/architecture/<type>.mermaid`** (raw source) and keep it **identical** to the body inside the fenced ` ```mermaid ` block in `ARCHITECTURE.md`; omit files for `N/A` or no diagram — see `workflows/crystallize.md` Step 4.
 
 ### Step 5: Generate PROJECT-CONTEXT.md
-- **FEAT-009:** Block `## ViePilot active profile (FEAT-009)` khi có binding
+- **FEAT-009:** Block `## ViePilot active profile (FEAT-009)` when binding is present
 - Domain knowledge
 - Business rules
 - Conventions
 - Constraints
-- Fill **`<product_vision>`** from template (`templates/project/PROJECT-CONTEXT.md`): MVP boundary, Post-MVP / Future themes, anti-goals — aligned with brainstorm horizon + Step 1 inventory
+- Fill **`<product_vision>`** from template (`templates/project/PROJECT-CONTEXT.md`): Project scope, Phase overview, anti-goals — aligned with brainstorm `## Phases` + Step 1 phases_inventory
 
 ### Step 6: Generate SYSTEM-RULES.md
 - Architecture rules
@@ -165,9 +177,9 @@ Ask user for (confirm proposals từ profile nếu có):
 - Stack-specific rules from cache
 
 ### Step 7: Generate ROADMAP.md
-- Use `templates/project/ROADMAP.md` — **executable MVP phases** first (tasks, criteria, verification)
-- **Mandatory `## Post-MVP / Product horizon`:** epic-level deferred work from horizon inventory **or** explicit single-release statement (no silent omission)
-- **Self-check before finalize:** non-empty horizon inventory must appear in ROADMAP; if mismatch → stop and ask user — see `workflows/crystallize.md` Step 7
+- Use `templates/project/ROADMAP.md` — phases in order (Phase 1, Phase 2...) from `phases_inventory`; no Post-MVP block
+- Each phase: tasks, acceptance criteria, verification commands
+- **Self-check before finalize:** all phases from phases_inventory appear in ROADMAP; if mismatch → stop and ask user — see `workflows/crystallize.md` Step 7
 
 ### Step 8: Generate schemas/
 - database-schema.sql
@@ -201,13 +213,13 @@ Ask user for (confirm proposals từ profile nếu có):
 - [ ] All artifacts created in .viepilot/
 - [ ] PROJECT-META.md has complete metadata
 - [ ] SYSTEM-RULES.md has all standards
-- [ ] Step 1 horizon extracted or explicit single-release recorded; validation gate satisfied
+- [ ] Step 1 phase assignment gate satisfied (phases_inventory recorded, all features assigned)
 - [ ] PROJECT-CONTEXT.md includes populated **`<product_vision>`** (template placeholders filled from brainstorm)
-- [ ] ROADMAP.md has MVP phases with tasks **and** mandatory Post-MVP / horizon block (or explicit single-release statement)
+- [ ] ROADMAP.md has phases with tasks in order from phases_inventory
 - [ ] TRACKER.md initialized
 - [ ] Project files created
 - [ ] Git committed
 - [ ] ARCHITECTURE diagram matrix is present and consistent (`required|optional|N/A`)
-- [ ] **ENH-022:** Mỗi diagram Mermaid được sinh có file `.viepilot/architecture/<canonical-name>.mermaid` đồng bộ nội dung với `ARCHITECTURE.md` (không tạo file thừa cho N/A)
-- [ ] **FEAT-009:** Nếu có profile bound — ARCHITECTURE + PROJECT-CONTEXT ghi nguồn profile; nếu không — ghi rõ none / not configured
+- [ ] **ENH-022:** Every generated Mermaid diagram has a `.viepilot/architecture/<canonical-name>.mermaid` file in sync with `ARCHITECTURE.md` (no extra files created for N/A)
+- [ ] **FEAT-009:** When profile is bound — ARCHITECTURE + PROJECT-CONTEXT record the profile source; if not — state none / not configured explicitly
 </success_criteria>

package/skills/vp-debug/SKILL.md

@@ -25,12 +25,12 @@ Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`,
 <implementation_routing_guard>
 ## Implementation routing guard (ENH-021)
 
-- **Điều tra + log** session; **không** merge fix shipping mặc định cho đến khi user **explicit** (*sửa luôn*, *hotfix*) hoặc route **`/vp-request` → `/vp-evolve` → `/vp-auto`**. Patch nhỏ chỉ để **reproduce** OK nếu user đồng ý. Xem `workflows/debug.md`.
+- **Investigate + log** session; does **not** merge default shipping fixes until user **explicit** (*fix now*, *hotfix*) or routes **`/vp-request` → `/vp-evolve` → `/vp-auto`**. Small patches only to **reproduce** are OK if the user agrees. See `workflows/debug.md`.
 </implementation_routing_guard>
 
 
 <objective>
-Systematic debugging với persistent state tracking. Giúp track vấn đề qua nhiều sessions.
+Systematic debugging with persistent state tracking. Helps track issues across multiple sessions.
 
 **Creates/Updates:**
 - `.viepilot/debug/session-{id}.json` - Debug session state

package/skills/vp-docs/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: vp-docs
-description: "Generate comprehensive documentation cho dự án"
+description: "Generate comprehensive documentation for the project"
 version: 0.2.1
 ---
 
@@ -10,7 +10,7 @@ version: 0.2.1
 - Treat all user text after the skill mention as `{{VP_ARGS}}`
 
 ## B. User Prompting
-Prompt user conversationally với options.
+Prompt user conversationally with options.
 
 ## C. Tool Usage
 Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`, `WebFetch`, `Subagent`
@@ -25,12 +25,12 @@ Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`,
 <implementation_routing_guard>
 ## Implementation routing guard (ENH-021)
 
-- Skill này sửa **`docs/`**, index, README liên quan doc — **không** implement **`lib/`**, **`tests/`**, logic product mặc định; việc đó là **`/vp-auto`**. Override explicit. Xem `workflows/request.md`.
+- This skill edits **`docs/`**, index, README related to docs — does **not** implement **`lib/`**, **`tests/`**, default product logic; that is **`/vp-auto`**. Explicit override required. See `workflows/request.md`.
 </implementation_routing_guard>
 
 
 <objective>
-Generate comprehensive documentation từ code và artifacts.
+Generate comprehensive documentation from code and artifacts.
 
 **Creates/Updates:**
 ```
@@ -60,7 +60,7 @@ CHANGELOG.md (updated)
 - GitHub owner/repo from `git remote get-url origin`
 - Skills count from `ls skills/*/SKILL.md | wc -l`
 - Workflows count from `ls workflows/*.md | wc -l`
-- **FEAT-009:** Optional ViePilot global profile từ `.viepilot/META.md` + `~/.viepilot/profiles/` cho attribution/tone (`workflows/documentation.md` §0A)
+- **FEAT-009:** Optional ViePilot global profile from `.viepilot/META.md` + `~/.viepilot/profiles/` for attribution/tone (`workflows/documentation.md` §0A)
 </objective>
 
 <execution_context>
@@ -98,7 +98,7 @@ ACTUAL_WORKFLOWS=$(ls workflows/*.md 2>/dev/null | wc -l | tr -d ' ')
 
 ### Step 0A: ViePilot active profile (FEAT-009)
 
-Sau Step 0: resolve `.viepilot/META.md` → file profile global (cùng quy tắc `workflows/crystallize.md`). Giữ working notes (org, website, audience, branding) cho prose docs; **không** fail nếu thiếu. Chi tiết: `workflows/documentation.md` §0A.
+After Step 0: resolve `.viepilot/META.md` → global profile file (same rules as `workflows/crystallize.md`). Keep working notes (org, website, audience, branding) for prose docs; do **not** fail if missing. Details: `workflows/documentation.md` §0A.
 
 ### Step 1: Ask Documentation Scope
 ```
@@ -273,5 +273,5 @@ View at: docs/README.md
 - [ ] skills-reference.md has sections for all skills in skills/ directory
 - [ ] Root README.md Documentation table updated
 - [ ] Git committed
-- [ ] **FEAT-009:** Nếu có profile — dùng cho attribution khi phù hợp; nếu không — bỏ qua im lặng (không placeholder sai)
+- [ ] **FEAT-009:** If profile exists — use for attribution where appropriate; if not — silently skip (no incorrect placeholders)
 </success_criteria>

package/skills/vp-evolve/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: vp-evolve
-description: "Nâng cấp, thêm features, hoặc bắt đầu milestone mới"
+description: "Upgrade, add features, or start a new milestone"
 version: 0.3.0
 ---
 
@@ -10,7 +10,7 @@ version: 0.3.0
 - Treat all user text after the skill mention as `{{VP_ARGS}}`
 
 ## B. User Prompting
-Prompt user conversationally với options.
+Prompt user conversationally with options.
 
 ## C. Tool Usage
 Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`, `WebFetch`, `Subagent`
@@ -25,28 +25,28 @@ Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`,
 <implementation_routing_guard>
 ## Implementation routing guard (ENH-021)
 
-- Skill này chỉ **planning**: ROADMAP, phase dir, SPEC/tasks, TRACKER, ghi chú version/CHANGELOG khi workflow quy định — **không** implement mã shipping mặc định (`lib/`, `tests/`, `bin/`, sửa lớn `workflows/`/`skills/` ngoài plan artifact).
-- **Bước tiếp:** **`/vp-auto`**. Xem `workflows/evolve.md`.
-- **Ngoại lệ:** User **explicit** bypass — nêu rõ trong chat.
+- This skill is **planning only**: ROADMAP, phase dir, SPEC/tasks, TRACKER, version/CHANGELOG notes when the workflow specifies — does **not** implement default shipping code (`lib/`, `tests/`, `bin/`, large edits to `workflows/`/`skills/` beyond plan artifacts).
+- **Next step:** **`/vp-auto`**. See `workflows/evolve.md`.
+- **Exception:** User **explicit** bypass — state clearly in chat.
 </implementation_routing_guard>
 
 
 <objective>
-Nâng cấp hoặc mở rộng dự án sau khi hoàn thành milestone hoặc cần thêm features.
+Upgrade or expand the project after completing a milestone or when new features are needed.
 
 **Modes:**
-1. **Add Feature** - Thêm feature vào milestone hiện tại
-2. **New Milestone** - Bắt đầu milestone mới
-3. **Refactor** - Cải thiện code hiện có
+1. **Add Feature** - Add a feature to the current milestone
+2. **New Milestone** - Start a new milestone
+3. **Refactor** - Improve existing code
 
 **Routing intelligence:**
-- Với yêu cầu thiên về khám phá ý tưởng (đặc biệt landing page), ưu tiên route qua `/vp-brainstorm` nâng cao trước khi crystallize phase.
-- Hỗ trợ route brainstorm có in-session research để user quyết định ngay trong một phiên.
+- For requests leaning toward idea exploration (especially landing pages), prioritize routing through enhanced `/vp-brainstorm` before the crystallize phase.
+- Supports brainstorm routing with in-session research so the user can decide within a single session.
 
 **Updates:**
 - `.viepilot/ROADMAP.md`
 - `.viepilot/TRACKER.md`
-- `.viepilot/ARCHITECTURE.md` (nếu có changes)
+- `.viepilot/ARCHITECTURE.md` (if there are changes)
 - `CHANGELOG.md`
 </objective>
 
@@ -59,6 +59,19 @@ Optional flags:
 - `--feature` : Add feature mode
 - `--milestone` : New milestone mode
 - `--refactor` : Refactor mode
+
+**Task path convention (BUG-009):**
+When generating task files, ALL paths in `## Paths` blocks MUST be
+repo-relative (relative to the repository root where `package.json` lives).
+
+```
+CORRECT:   workflows/foo.md   skills/vp-bar/SKILL.md   lib/foo.cjs
+INCORRECT: ~/.claude/viepilot/workflows/foo.md   /absolute/path
+```
+
+Absolute paths inside code block content (bash examples, runtime descriptions)
+are fine — only the `## Paths` header block must use repo-relative paths.
+See guard in `workflows/evolve.md` → "TASK PATH RULE (BUG-009)".
 </context>
 
 <process>

package/skills/vp-info/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: vp-info
-description: "Hiển thị phiên bản ViePilot, npm latest, danh sách skills/workflows qua vp-tools"
+description: "Display ViePilot version, npm latest, skills/workflows list via vp-tools"
 version: 0.1.1
 ---
 
@@ -22,21 +22,21 @@ Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`,
 <implementation_routing_guard>
 ## Implementation routing guard (ENH-021)
 
-- **Inventory / version info** — không implement shipping; implement qua **`/vp-auto`**. Xem `workflows/request.md`.
+- **Inventory / version info** — does not implement shipping; implement via **`/vp-auto`**. See `workflows/request.md`.
 </implementation_routing_guard>
 
 
 <objective>
-Chạy **`vp-tools info`** để lấy metadata bundle ViePilot (không cần `.viepilot/` trong project đích).
+Run **`vp-tools info`** to retrieve the ViePilot bundle metadata (no `.viepilot/` needed in the target project).
 
-**Output hữu ích cho agent:**
+**Useful output for agents:**
 - `installedVersion`, `packageName`, `packageRoot`
-- `latestNpm` (ok + version hoặc lỗi mạng/registry)
-- `gitHead` (nếu clone có git)
+- `latestNpm` (ok + version or network/registry error)
+- `gitHead` (if clone has git)
 - `skills[]`: `id`, `version`, `relativePath`
 - `workflows[]`: `id`, `relativePath`, `note`
 
-Dùng **`vp-tools info --json`** khi cần parse hoặc so sánh phiên bản trong script.
+Use **`vp-tools info --json`** when parsing or comparing versions in scripts.
 </objective>
 
 <execution_context>
@@ -46,30 +46,30 @@ Dùng **`vp-tools info --json`** khi cần parse hoặc so sánh phiên bản tr
 <process>
 
 ### Step 1: Resolve CLI
-Ưu tiên theo thứ tự:
-1. `vp-tools info` — khi ViePilot đã có trên `PATH` (npm global hoặc shim).
-2. `node <viepilot-package>/bin/vp-tools.cjs info` — từ repo clone hoặc `node_modules/viepilot`.
+Priority order:
+1. `vp-tools info` — when ViePilot is already on `PATH` (npm global or shim).
+2. `node <viepilot-package>/bin/vp-tools.cjs info` — from repo clone or `node_modules/viepilot`.
 
-### Step 2: Chạy lệnh
+### Step 2: Run command
 ```bash
 vp-tools info
-# hoặc
+# or
 vp-tools info --json
 ```
 
-### Step 3: Diễn giải JSON (khi dùng `--json`)
-- **`packageRoot`**: gốc package `viepilot` CLI đang resolve được.
-- **`installedVersion`**: semver trong `package.json` của bundle đó.
-- **`latestNpm`**: `{ ok, version }` hoặc `{ ok: false, error }`.
-- **`skills`**: inventory skill trong `skills/*/SKILL.md` (version từ frontmatter).
-- **`workflows`**: file `workflows/*.md`.
+### Step 3: Interpret JSON (when using `--json`)
+- **`packageRoot`**: root of the `viepilot` package the CLI resolved.
+- **`installedVersion`**: semver in `package.json` of that bundle.
+- **`latestNpm`**: `{ ok, version }` or `{ ok: false, error }`.
+- **`skills`**: skill inventory in `skills/*/SKILL.md` (version from frontmatter).
+- **`workflows`**: files in `workflows/*.md`.
 
-### Step 4: Lỗi thường gặp
-Nếu báo không tìm thấy package root: cài global (`npm i -g viepilot`), hoặc chạy từ project có dependency `viepilot`, hoặc trỏ thẳng tới `bin/vp-tools.cjs` trong clone.
+### Step 4: Common errors
+If package root is not found: install globally (`npm i -g viepilot`), or run from a project that has `viepilot` as a dependency, or point directly to `bin/vp-tools.cjs` in a clone.
 </process>
 
 <success_criteria>
-- [ ] Đã gọi đúng subcommand `info` (hoặc `--json` khi cần parse)
-- [ ] Nêu rõ `installedVersion` và (nếu có) `latestNpm.version`
-- [ ] Khi user hỏi “có những skill nào trong bundle”, tóm tắt từ `skills[]` hoặc output bảng CLI
+- [ ] Correct subcommand `info` called (or `--json` when parsing is needed)
+- [ ] `installedVersion` and (if available) `latestNpm.version` clearly stated
+- [ ] When user asks “what skills are in the bundle”, summarize from `skills[]` or CLI table output
 </success_criteria>

package/skills/vp-pause/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: vp-pause
-description: "Pause work với context preservation để resume sau"
+description: "Pause work with context preservation to resume later"
 version: 0.1.1
 ---
 
@@ -10,7 +10,7 @@ version: 0.1.1
 - Treat all user text after the skill mention as `{{VP_ARGS}}`
 
 ## B. User Prompting
-Prompt user conversationally để gather state info.
+Prompt user conversationally to gather state info.
 
 ## C. Tool Usage
 Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`, `WebFetch`, `Subagent`
@@ -25,19 +25,19 @@ Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`,
 <implementation_routing_guard>
 ## Implementation routing guard (ENH-021)
 
-- **Handoff state** — không implement shipping; resume với **`/vp-resume`** rồi **`/vp-auto`** theo plan. Xem `workflows/request.md`.
+- **Handoff state** — does not implement shipping; resume with **`/vp-resume`** then **`/vp-auto`** per plan. See `workflows/request.md`.
 </implementation_routing_guard>
 
 
 <objective>
-Save complete work state để có thể resume từ bất kỳ context nào.
+Save complete work state so it can be resumed from any context.
 
 **Creates/Updates:**
 - `.viepilot/HANDOFF.json` - Machine-readable state
 - `.viepilot/phases/{current}/.continue-here.md` - Human-readable context
 - Git WIP commit
 
-**After:** Safe to close session. Resume với `/vp-resume`
+**After:** Safe to close session. Resume with `/vp-resume`
 </objective>
 
 <execution_context>