vp-request

name	vp-request
description	Create new request: feature, bug fix, enhancement, or brainstorm continuation
version	0.2.0

## Invocation Banner

Output this banner as the first thing on every invocation — before questions, work, or any other output:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 VIEPILOT ► VP-REQUEST  v0.2.0 (fw 2.19.0)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

## Version Update Check (ENH-072)

After displaying the greeting banner, run:

node "$HOME/.claude/viepilot/bin/vp-tools.cjs" check-update --silent

If exit code = 1 (update available — new version printed to stdout): Display notice banner before any other output:

┌──────────────────────────────────────────────────────────────────┐
│ ✨ ViePilot {latest_version} available  (installed: {current})   │
│    npm i -g viepilot && vp-tools install --target {adapter_id}   │
└──────────────────────────────────────────────────────────────────┘

Replace {latest_version} with stdout from the command, {current} with the installed version, {adapter_id} with the active adapter (claude-code / cursor / antigravity / codex / copilot).

If exit code = 0 or command unavailable: silent, continue.

Suppression rules:

• --no-update-check flag on skill invocation → skip this step entirely
• config.json → update.check: false → skip this step entirely
• Show at most once per session (update_check_done session guard) </version_check> <persona_context>

Persona Context Injection (ENH-073)

At skill start, run:

node "$HOME/.claude/viepilot/bin/vp-tools.cjs" persona auto-switch
node "$HOME/.claude/viepilot/bin/vp-tools.cjs" persona context

Inject the output as ## User Persona context before any task execution. Silent if command unavailable or errors. </persona_context>

## A. Skill Invocation - Skill được gọi khi user mention `vp-request`, `/vp-request`, "request", "yêu cầu", "bug", "lỗi", "feature mới", "nâng cấp" - Treat all user text after the skill mention as `{{VP_ARGS}}`

B. User Prompting

Prompt user conversationally with numbered list options.

C. Tool Usage

Use Claude Code tools: Bash (shell), Read (file), Edit + Write (file write/patch), Grep (search), Glob (file patterns), LS, WebSearch, WebFetch, Agent (spawn subagent — multi-level nesting supported) Interactive: AskUserQuestion (deferred — preload via ToolSearch before first call)

## A. Skill Invocation Same trigger keywords as claude-code adapter.

C. Tool Usage

Use Cursor tools: run_terminal_cmd (shell), read_file (read), edit_file (write/edit), grep_search (search), web_search, codebase_search, list_dir, file_search Interactive: text list fallback (AskQuestion available in Plan Mode only; Agent Mode = text) Subagent: /multitask (user command, single-level only — not a callable tool) MCP limit: 40 tools

## A. Skill Invocation Same trigger keywords as claude-code adapter. Skill discovery: LLM-driven (automatic, no slash command needed).

C. Tool Usage

Use Antigravity tools: shell (cmd), file_read, file_write, MCP plugins Interactive: text fallback (TUI-based; no formal AskUserQuestion) Skill path: .agents/skills/<skill>/SKILL.md (project) or ~/.gemini/antigravity/skills/ (global) Note: Gemini CLI deprecated June 18, 2026 — use Antigravity CLI.

## A. Skill Invocation Same trigger keywords as claude-code adapter.

C. Tool Usage

Use Codex tools: container.exec (sandboxed shell), apply_patch (file write), web_search Interactive: text fallback (TUI Tab/Enter injection) Config: ~/.codex/config.toml

## A. Skill Invocation Same trigger keywords as claude-code adapter. Discovery: User-driven (`@agent-name` in GitHub Copilot Chat).

C. Tool Usage

Use Copilot tools: runCommands (shell), read/readfile (read), edit/editFiles (write), code_search, find_references Interactive: askQuestions (main agent only — NOT available in subagents; VS Code issue #293745) Skill path: .github/agents/<name>.agent.md <scope_policy>

ViePilot Namespace Guard (BUG-004)

• Default mode: only use and reference vp-* skills in ViePilot workflows.
• External skills (non vp-*) are out of framework scope unless user explicitly opts in.
• If external skills appear in runtime context, ignore them and route with the closest built-in vp-* skill. </scope_policy>

<implementation_routing_guard>

Implementation routing guard (ENH-021)

• This skill only creates requests, backlog, triage (.viepilot/requests/*, TRACKER, sometimes suggests ROADMAP) — does not implement default shipping code (lib/, tests/, bin/, workflows/, skills/ of the repo, etc.).
• After request: /vp-evolve (ROADMAP + phase + tasks + plan) → /vp-auto (execute). See workflows/request.md.
• Exception: User explicit (hotfix now, fix in this chat, bypass planning) — must state clearly the bypass in chat.
• Do not suggest ”Start working now” as direct implementation in this thread; use evolve → auto instead. </implementation_routing_guard>

Create and manage requests for the project under development: - Bug report and fix - Feature request - Enhancement/Improvement - Technical debt - Brainstorm continuation for new ideas

Creates/Updates:

• .viepilot/requests/{TYPE}-{NUMBER}.md
• .viepilot/TRACKER.md (add to backlog)
• .viepilot/ROADMAP.md (if approved)

Routes to: /vp-auto or /vp-evolve depending on request type

<execution_context> @$HOME/{envToolDir}/workflows/request.md </execution_context>

Optional flags: - `--bug` : Bug report mode - `--feature` : Feature request mode - `--enhance` : Enhancement mode - `--debt` : Technical debt mode - `--brainstorm` : Brainstorm continuation mode - `--list` : List pending requests - `--quick` : Quick mode (minimal questions)

URL Auto-Enrichment (ENH-093)

If your request originates from an existing issue tracker, pass the URL directly:

/vp-request https://github.com/org/repo/issues/123
/vp-request https://company.atlassian.net/browse/PROJ-456
/vp-request https://trello.com/c/cardId/card-title
/vp-request https://linear.app/team/issue/ENG-789
/vp-request https://notion.so/page-slug-abc123

ViePilot automatically extracts: title, type, description, priority — you confirm or edit. Requires: browser-intake-agent + vercel-labs/agent-browser (npx skills add vercel-labs/agent-browser).

Supported sources: GitHub Issues, Linear, Jira (Atlassian), Trello, Notion.

When extraction is unavailable (non-CC adapter or agent-browser not installed), the URL is stored as a related_url field in the request file and the normal question flow proceeds.

Execute workflow from `@$HOME/{envToolDir}/workflows/request.md`

Step 1: Detect Request Type

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 VIEPILOT ► REQUEST
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

What type of request?

1. 🐛 Bug Report - Something is broken
2. ✨ Feature Request - New functionality
3. 🔧 Enhancement - Improve existing feature
4. 🧹 Technical Debt - Code cleanup/refactor
5. 💡 Brainstorm - Explore new ideas
6. 📋 List Requests - View pending requests

Step 2: Gather Request Details

For Bug Report (🐛)

Bug Details:

1. Title/Summary?
2. What happened? (actual behavior)
3. What should happen? (expected behavior)
4. Steps to reproduce?
5. Which part of system? (service/module)
6. Severity? (critical/high/medium/low)
7. Any error messages/logs?

For Feature Request (✨)

Feature Details:

1. Title/Summary?
2. What problem does it solve?
3. Describe the feature
4. Who benefits from this?
5. Priority? (must-have/should-have/nice-to-have)
6. Any specific requirements?

Do you want to brainstorm this feature in detail? (y/n)
→ If yes: route to mini brainstorm session

For Enhancement (🔧)

Enhancement Details:

1. Title/Summary?
2. Which existing feature to enhance?
3. Current behavior
4. Desired improvement
5. Why is this valuable?
6. Breaking changes? (yes/no)

For Technical Debt (🧹)

Tech Debt Details:

1. Title/Summary?
2. What needs cleanup?
3. Current issues (performance/maintainability/etc)
4. Proposed solution
5. Effort estimate? (S/M/L/XL)
6. Risk if not addressed?

For Brainstorm (💡)

Brainstorm Topic:

1. What do you want to explore?
2. Related to existing feature or completely new?
3. Any initial ideas?

→ Route to full brainstorm session with context

Step 3: Create Request File

Create .viepilot/requests/{TYPE}-{NUMBER}.md:

# {TYPE}: {TITLE}

## Meta
- **ID**: {TYPE}-{NUMBER}
- **Type**: Bug | Feature | Enhancement | Tech Debt
- **Status**: new | triaged | in_progress | done | wont_fix
- **Priority**: critical | high | medium | low
- **Created**: {timestamp}
- **Reporter**: User
- **Assignee**: AI

## Summary
{SUMMARY}

## Details
{DETAILS_BASED_ON_TYPE}

## Acceptance Criteria
- [ ] {criteria_1}
- [ ] {criteria_2}

## Related
- Phase: {if linked to phase}
- Files: {affected files}
- Dependencies: {related requests}

## Discussion
{Any additional context from brainstorm}

## Resolution
{Filled when resolved}

Step 4: Triage & Route

Based on request type and priority:

Critical Bug:

⚠️ Critical bug detected!

Options:
1. Fix immediately (pause current work)
2. Add to top of current phase
3. Schedule for next available slot

Feature/Enhancement:

Request logged: {TYPE}-{NUMBER}

Options:
1. Add to current milestone backlog
2. Brainstorm in detail first
3. Schedule for next milestone
4. Plan then execute: `/vp-evolve` → `/vp-auto` (not direct implement here unless explicit override)

Tech Debt:

Tech debt logged: {TYPE}-{NUMBER}

Options:
1. Add to refactor backlog
2. Include in next phase
3. Create dedicated cleanup phase

Step 5: Update Tracking

Update .viepilot/TRACKER.md:

## Backlog

### Pending Requests
| ID | Type | Title | Priority | Status |
|----|------|-------|----------|--------|
| BUG-001 | 🐛 | Login timeout | high | new |
| FEAT-002 | ✨ | Export feature | medium | triaged |

Step 6: Confirm & Next Steps

Display confirmation banner:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 VIEPILOT ► REQUEST CREATED ✓
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

 ID: {TYPE}-{NUMBER}
 Type: {TYPE}
 Title: {TITLE}
 Priority: {PRIORITY}
 Status: {STATUS}

 File: .viepilot/requests/{TYPE}-{NUMBER}.md
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Claude Code (terminal) — REQUIRED: After banner, call AskUserQuestion:

question: "Request {TYPE}-{N} logged. What would you like to do next?"
options:
  - label: "Plan phase + tasks → /vp-evolve"
    description: "Create ROADMAP entry, phase dir, and task files now (Recommended)"
  - label: "Create another request → /vp-request"
    description: "Log more requests before planning"
  - label: "Done for now"
    description: "Exit — request is saved in backlog"

On selection:

• "Plan phase + tasks → /vp-evolve": invoke /vp-evolve skill
• "Create another request → /vp-request": invoke /vp-request skill
• "Done for now": print "Request {TYPE}-{N} saved in backlog." and exit

Text fallback (Cursor/Codex/Copilot/Antigravity):

Next actions:
  /vp-evolve    Plan phase/tasks + ROADMAP
  /vp-request   Create another request

<success_criteria>

• Request type identified
• Details gathered appropriately
• Request file created
• TRACKER.md updated
• Appropriate routing suggested </success_criteria>

Adapter Compatibility

AskUserQuestion Tool (ENH-048)

This skill uses adapter-aware interactive prompts. Behavior depends on your adapter:

Adapter	Interactive Prompts	Notes
Claude Code (terminal)	✅ AskUserQuestion tool — REQUIRED	Must call AUQ; plain-text only if tool errors or is unavailable
Claude Code (VS Code ext)	⚠️ Partial	Terminal yes; VS Code UI pending anthropics/claude-code#12609
Cursor (Plan Mode)	⚠️ Partial	AskQuestion in Plan Mode only — not in Agent/Skills Mode
Cursor (Agent/Skills)	❌ Text fallback	AskQuestion not available in Agent Mode
Codex CLI	❌ Text fallback	Native tool N/A; community MCP available
Antigravity (native agent)	❌ Text fallback	Artifact model, no raw tool calls
GitHub Copilot	✅ /skill-name in Chat	Via .agent.md custom agent; AUQ not available — text fallback

Claude Code (terminal) — AUQ preload required (ENH-059): Before the first interactive prompt, call ToolSearch with query: "select:AskUserQuestion" to load the deferred tool schema. Only after ToolSearch succeeds can AskUserQuestion be invoked. If ToolSearch returns an error, fall back to plain-text numbered list for that session.

When AskUserQuestion is not available on other adapters, the skill automatically falls back to plain-text numbered list prompts — no configuration required.

Prompts using AskUserQuestion in this skill:

• Request type detection (Bug / Feature / Enhancement / Tech Debt — Step 2)
• Bug severity selection (Critical / High / Medium / Low — Step 4A)
• Feature priority selection (Must-have / Should-have / Nice-to-have — Step 4B)
• Workflow continuation (Step 6 — Plan /vp-evolve / Create another / Done)