viepilot 2.4.0 → 2.15.0

package/workflows/documentation.md

@@ -17,20 +17,35 @@ Generate comprehensive documentation from code and artifacts.
 Before generating any file, collect actual project context from the environment:
 
 ```bash
-# Get GitHub remote URL (supports both HTTPS and SSH formats)
+# Get Git remote URL (supports any forge: GitHub, GitLab, Bitbucket, Azure DevOps, Gitea, self-hosted)
 REMOTE_URL=$(git remote get-url origin 2>/dev/null || echo "")
 
-# Extract owner/repo slug
-# https://github.com/0-CODE/viepilot.git → 0-CODE/viepilot
-# git@github.com:0-CODE/viepilot.git → 0-CODE/viepilot
-GITHUB_SLUG=$(echo "$REMOTE_URL" | sed 's|.*github\.com[:/]||; s|\.git$||')
-GITHUB_OWNER=$(echo "$GITHUB_SLUG" | cut -d'/' -f1)
-GITHUB_REPO=$(echo "$GITHUB_SLUG" | cut -d'/' -f2)
+# Forge-agnostic remote URL parser
+# Handles SSH  : git@<host>:owner/repo.git
+# Handles HTTPS: https://<host>/owner/repo.git
+# Handles Azure DevOps: https://dev.azure.com/org/project/_git/repo
+if echo "$REMOTE_URL" | grep -q 'dev\.azure\.com'; then
+  # Azure DevOps: https://dev.azure.com/ORG/PROJECT/_git/REPO
+  GIT_HOST="dev.azure.com"
+  GIT_OWNER=$(echo "$REMOTE_URL" | sed 's|.*dev\.azure\.com/||; s|/.*||')
+  GIT_REPO=$(echo "$REMOTE_URL" | sed 's|.*/_git/||; s|\.git$||; s|/$||')
+elif echo "$REMOTE_URL" | grep -q '^git@'; then
+  # SSH format: git@host:owner/repo.git
+  GIT_HOST=$(echo "$REMOTE_URL" | sed 's|^git@||; s|:.*||')
+  GIT_OWNER=$(echo "$REMOTE_URL" | sed 's|^git@[^:]*:||; s|/.*||')
+  GIT_REPO=$(echo "$REMOTE_URL" | sed 's|^git@[^:]*:[^/]*/||; s|\.git$||')
+else
+  # HTTPS format: https://host/owner/repo.git
+  GIT_HOST=$(echo "$REMOTE_URL" | sed 's|^https\?://||; s|/.*||')
+  GIT_OWNER=$(echo "$REMOTE_URL" | sed 's|^https\?://[^/]*/||; s|/.*||')
+  GIT_REPO=$(echo "$REMOTE_URL" | sed 's|^https\?://[^/]*/[^/]*/||; s|\.git$||; s|/$||')
+fi
 
 # Fallback if no remote
-if [ -z "$GITHUB_OWNER" ]; then
-  GITHUB_OWNER="{GITHUB_OWNER}"
-  GITHUB_REPO="{GITHUB_REPO}"
+if [ -z "$GIT_OWNER" ]; then
+  GIT_HOST="{GIT_HOST}"
+  GIT_OWNER="{GIT_OWNER}"
+  GIT_REPO="{GIT_REPO}"
 fi
 
 # Get project name from package.json or directory name
@@ -54,7 +69,7 @@ if [ -d "skills" ] && ls skills/vp-*/SKILL.md 2>/dev/null | head -1 > /dev/null;
 fi
 ```
 
-Use `$GITHUB_OWNER`, `$GITHUB_REPO` throughout all generated files.
+Use `$GIT_HOST`, `$GIT_OWNER`, `$GIT_REPO` throughout all generated files.
 For viepilot framework repos, also use `$ACTUAL_SKILLS`, `$ACTUAL_WORKFLOWS`.
 **Never hardcode** `your-org`, `YOUR_USERNAME`, `YOUR_ORG`, or static skill/workflow counts.
 

package/workflows/evolve.md

@@ -2,6 +2,14 @@
 Upgrade or expand the project: add features, start a new milestone, or refactor.
 </purpose>
 
+## Adapter Compatibility
+
+| Feature | Claude Code (terminal) | Cursor (Agent/Skills) | Codex CLI | Antigravity (native) |
+|---------|----------------------|-----------------------|-----------|----------------------|
+| Interactive prompts | ✅ `AskUserQuestion` tool | ❌ text fallback | ❌ text fallback | ❌ text fallback |
+
+When `AskUserQuestion` is not available, each prompt block falls back to the plain-text numbered list shown below it — no configuration needed.
+
 ## ViePilot Skill Scope Policy (BUG-004)
 
 - Default behavior: only use and suggest skills under `vp-*`.
@@ -44,7 +52,17 @@ Determine:
  Version: {version}
 
 How would you like to evolve the project?
+```
+
+> **Adapter-aware prompt:**
+> - **Claude Code (terminal):** use `AskUserQuestion` tool — spec:
+>   - question: "How would you like to evolve the project?"
+>   - header: "Evolve mode"
+>   - options: [{ label: "Add Feature", description: "Add a new capability to the current milestone" }, { label: "New Milestone", description: "Archive current milestone and start a new scope" }, { label: "Refactor", description: "Improve existing code without adding new features" }]
+>   - multiSelect: false
+> - **Cursor / Codex / Antigravity / other:** use text menu below
 
+```
 1. Add Feature - Add new feature to current milestone
 2. New Milestone - Start a new milestone (archive current)
 3. Refactor - Improve existing code without new features
@@ -62,7 +80,25 @@ Describe the new feature:
 2. What does it do? (1-2 sentences)
 3. Which services/modules affected?
 4. Dependencies on existing code?
+
+> **Adapter-aware prompt (question 5 — complexity):**
+> - **Claude Code (terminal):** use `AskUserQuestion` tool — spec:
+>   - question: "Estimated implementation complexity?"
+>   - header: "Complexity"
+>   - options: [{ label: "S — Small", description: "Few hours — isolated change, 1 file" }, { label: "M — Medium", description: "1–2 days — 1–2 files, some integration" }, { label: "L — Large", description: "3–5 days — multiple modules affected" }, { label: "XL — Extra Large", description: "1+ week — architectural change or major feature" }]
+>   - multiSelect: false
+> - **Cursor / Codex / Antigravity / other:** use text below
+
 5. Estimated complexity? (S/M/L/XL)
+
+> **Adapter-aware prompt (question 6 — brainstorm routing):**
+> - **Claude Code (terminal):** use `AskUserQuestion` tool — spec:
+>   - question: "Does this feature need a brainstorm session first?"
+>   - header: "Brainstorm?"
+>   - options: [{ label: "Yes — go to /vp-brainstorm", description: "Research-heavy, UX-driven, or landing page feature — brainstorm first" }, { label: "No — plan directly", description: "Scope is clear — proceed to phase/task planning now" }]
+>   - multiSelect: false
+> - **Cursor / Codex / Antigravity / other:** use text below
+
 6. Need deep brainstorm? (landing page / UX / growth ideas / research-heavy)
 ```