vp-resume

name	vp-resume
description	Resume work from previous session with full context restoration
version	0.1.1

## Invocation Banner

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

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 VIEPILOT ► VP-RESUME  v0.1.1 (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-resume`, `/vp-resume`, "resume", "tiếp tục", "where was i" - Treat all user text after the skill mention as `{{VP_ARGS}}`

B. User Prompting

Prompt user conversationally with 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)

• Restore context — does not implement default shipping; continue with /vp-auto when a task plan exists. See workflows/request.md. </implementation_routing_guard>

Restore complete project context and resume work seamlessly.

Reads:

• .viepilot/HANDOFF.json
• .viepilot/TRACKER.md
• .viepilot/phases/{phase}/.continue-here.md

After: Context restored, ready to continue or route to appropriate action.

<execution_context> @$HOME/{envToolDir}/workflows/resume-work.md </execution_context>

Execute workflow from `@$HOME/{envToolDir}/workflows/resume-work.md`

Step 1: Check Project Exists

ls .viepilot/TRACKER.md

If not exists → Error: "No ViePilot project found. Run /vp-crystallize first."

Step 2: Load State

Try HANDOFF.json first (preferred):

cat .viepilot/HANDOFF.json

Parse: phase, task, status, next_action, context_notes

Fallback to TRACKER.md:

cat .viepilot/TRACKER.md

Extract current state from Progress Overview section.

Load .continue-here.md if exists:

cat .viepilot/phases/{phase}/.continue-here.md

Step 3: Check Uncommitted Changes

git status --porcelain

If changes exist, warn user and ask how to proceed.

Step 4: Rebuild Context

Following AI-GUIDE.md strategy:

minimal_load:
  - AI-GUIDE.md
  - TRACKER.md
  - PHASE-STATE.md (current phase)

task_load:
  - tasks/{current_task}.md
  - context_required files from task

Step 5: Display State Summary

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 VIEPILOT ► RESUME
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

 Project: {project_name}
 Last Activity: {timestamp}

 Current State:
 ├── Phase: {phase_number} - {phase_name}
 ├── Task: {task_number}/{total} - {task_name}
 ├── Status: {status}
 └── Progress: [████████░░] {percent}%

 Context Notes:
 {context_notes from HANDOFF.json}

 Next Action:
 {next_action from HANDOFF.json}

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Step 6: Offer Options

Prompt user:

How would you like to proceed?

1. Continue from task {task} (recommended)
2. Restart current task
3. Skip to next task
4. View task details
5. Run /vp-status for full overview
6. Start /vp-auto for autonomous mode

Step 7: Route to Action

Based on user choice:

• Continue → Load task context, start working
• Restart → Reset task state, start fresh
• Skip → Mark task skipped, move to next
• View → Display task file content
• Status → Skill(skill="vp-status")
• Auto → Skill(skill="vp-auto", args="--from {phase}")

Step 8: Update Session

# Update TRACKER.md with session info
# Clear HANDOFF.json (now active)

<success_criteria>

• HANDOFF.json or TRACKER.md loaded
• Context rebuilt efficiently
• State summary displayed clearly
• User offered appropriate options
• Routed to correct next action
• Session continuity maintained </success_criteria>