副总裁简历
- 作者仓库星标 13
- 作者仓库 viepilot
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 92 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @0-CODE · v0.1.1 · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 运行环境要求
- Node.js
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 1 步:检查项目是否存在
如果不存在 → 错误:“未找到 ViePilot 项目。首先运行 `/vp-crystallize`。”
第2步:加载状态
首先尝试 HANDOFF.json(首选):解析:阶段、任务、状态、next_action、context_notes 回退到 TRACKER.md:从进度概述部分提取当前状态。如果存在则加载 .continue-here.md:
第 3 步:检查未提交的更改
如果存在更改,警告用户并询问如何继续。
第 4 步:重建上下文
遵循 AI-GUIDE.md 策略:
第 6 步:提供选项
提示用户:
第 7 步:行动路线
基于用户选择: 继续 → 加载任务上下文,开始工作 重新启动 → 重置任务状态,重新开始 跳过 → 标记任务已跳过,移至下一个 查看 → 显示任务文件内容
第 8 步:更新会话
</process> <success_criteria> [ ] HANDOFF.json 或 TRACKER.md 已加载 [ ] 上下文重建有效 [ ] 状态摘要显示清晰
<greeting>
## 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)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
```
</greeting>
<version_check>
## Version Update Check (ENH-072)
After displaying the greeting banner, run:
```bash
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:
```bash
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>
<adapter id="claude-code">
## 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)
</adapter>
<adapter id="cursor-agent">
## 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
</adapter>
<adapter id="antigravity">
## 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.
</adapter>
<adapter id="codex">
## 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`
</adapter>
<adapter id="copilot">
## 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`
</adapter>
<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>
<objective>
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.
</objective>
<execution_context>
@$HOME/{envToolDir}/workflows/resume-work.md
</execution_context>
<process>
Execute workflow from `@$HOME/{envToolDir}/workflows/resume-work.md`
### Step 1: Check Project Exists
```bash
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):**
```bash
cat .viepilot/HANDOFF.json
```
Parse: phase, task, status, next_action, context_notes
**Fallback to TRACKER.md:**
```bash
cat .viepilot/TRACKER.md
```
Extract current state from Progress Overview section.
**Load .continue-here.md if exists:**
```bash
cat .viepilot/phases/{phase}/.continue-here.md
```
### Step 3: Check Uncommitted Changes
```bash
git status --porcelain
```
If changes exist, warn user and ask how to proceed.
### Step 4: Rebuild Context
Following AI-GUIDE.md strategy:
```yaml
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
```bash
# Update TRACKER.md with session info
# Clear HANDOFF.json (now active)
```
</process>
<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>
章节与文件索引
按说明文件中的顺序排列。
召唤横幅
版本更新检查 (ENH-072)
角色上下文注入 (ENH-073)
A. 技能调用
B. 用户提示
文件/命令 -> {latest_version} · {current} · {adapter_id} · --no-update-check · config.json · update.check: false · update_check_done · ## User Persona
内容校验值 -> ca37d63a81e6
当前原文的自动摘译,尚未人工审校。
召唤横幅
将此横幅输出作为每次调用的第一件事 - 在问题、工作或任何其他输出之前:</greeting> <version_check>
版本更新检查 (ENH-072)
显示问候语横幅后,运行: 如果退出代码 = 1(可用更新 — 新版本打印到标准输出):在任何其他输出之前显示通知横幅:将
{latest_version}替换为命令中的 stdout,将{current}替换为已安装的版本,将{adapter_id}替换为活动适配器(claude-code/cursor/antigravity/codex/copilot)。角色上下文注入 (ENH-073)
在技能启动时,运行:在任何任务执行之前将输出作为
## User Persona上下文注入。如果命令不可用或出现错误,则保持沉默。 </persona_context> <适配器id =“claude-code”>A. 技能调用
技能 được gọi khi 用户提及
vp-resume、/vp-resume、“resume”、“tiếp tục”、“where was i” 将技能提及后的所有用户文本视为{{VP_ARGS}}B. 用户提示
以对话方式提示用户选项。