vp-task
- Repo stars 13
- Author updated Live
- Author repo viepilot
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 92 / 100 · audit passed
- Author / version / license
- @0-CODE · v0.2.0 · no license declared
- Token usage
- Lean
- Setup complexity
- Manual integration
- External API key
- Not required
- Operating systems
- Docker
- Runtime requirements
- Node.js · Docker
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: vp-task
description: Manual control over individual tasks Output this banner as the first thing on every invocation —…
category: other
runtime: Node.js / Docker
---
# vp-task output preview
## PART A: Task fit
- Use case: Manual control over individual tasks Output this banner as the first thing on every invocation — before questions, work, or any other output: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ VIEPILOT ► VP-TASK v0.2.0 (fw 2.19.0) runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Invocation Banner / Version Update Check (ENH-072) / Persona Context Injection (ENH-073)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Manual control over individual tasks Output this banner as the first thing on every invocation — before questions, work, or any other output: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ VIEPILOT ► VP-TASK v0.2.0 (fw 2.19.0) runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Invocation Banner / Version Update Check (ENH-072) / Persona Context Injection (ENH-073)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source mentions slash commands such as `/vp-task`, `/multitask`, `/vp-auto`, `/vp-evolve`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Invocation Banner / Version Update Check (ENH-072) / Persona Context Injection (ENH-073)”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: vp-task
description: Manual control over individual tasks Output this banner as the first thing on every invocation —…
category: other
source: 0-CODE/viepilot
---
# vp-task
## When to use
- Manual control over individual tasks Output this banner as the first thing on every invocation — before questions, wor…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Invocation Banner / Version Update Check (ENH-072) / Persona Context Injection (ENH-073)” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "vp-task" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Invocation Banner / Version Update Check (ENH-072) / Persona Context Injection (ENH-073)
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js / Docker | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Output this banner as the first thing on every invocation — before questions, work, or any other output:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
VIEPILOT ► VP-TASK v0.2.0 (fw 2.19.0)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
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-checkflag on skill invocation → skip this step entirelyconfig.json→update.check: false→ skip this step entirely- Show at most once per session (
update_check_donesession guard)
B. 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)
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
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.
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
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
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.
- This skill only manages state/tag/task in
.viepilot/— does not replace/vp-autofor implementing shipping code. To implement: use/vp-autoor user explicit override. Plan chain:/vp-evolvefirst. Seeworkflows/request.md.
Commands:
list- List tasks in current phaseshow N- Show task N detailsstart N- Manually start task Ndone N- Mark task N as doneskip N- Skip task N with reasonretry N- Retry failed task Nrollback N- Rollback task N
Parse Command
/vp-task {command} {args}
Commands:
- /vp-task list
- /vp-task show 3
- /vp-task start 3
- /vp-task done 3
- /vp-task skip 3 --reason "Not needed for Phase 1"
- /vp-task retry 3
- /vp-task rollback 3
Command: list
# Read current phase
cat .viepilot/TRACKER.md → current_phase
cat .viepilot/phases/{phase}/PHASE-STATE.md
Display:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Phase {N}: {Name} - Tasks
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
# │ Task │ Status │ Tag
───┼───────────────────────────┼─────────────┼─────────────
1 │ Create parent pom.xml │ ✅ done │ vp-p1-t1-done
2 │ Create common module │ ✅ done │ vp-p1-t2-done
3 │ Create tap-service │ 🔄 progress │ vp-p1-t3
4 │ Create location-service │ ⏳ pending │ -
5 │ Docker Compose setup │ ⏳ pending │ -
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Command: show N
cat .viepilot/phases/{phase}/tasks/{N}-*.md
Display task file content with syntax highlighting.
Command: start N
actions:
1. Check task not already started
2. Check dependencies met
3. Create git tag: vp-p{phase}-t{N}
4. Update PHASE-STATE.md: status → in_progress
5. Update TRACKER.md
6. Display task objective and acceptance criteria
Command: done N
actions:
1. Verify task exists and is in_progress
2. Ask: "Skip verification? (not recommended)"
3. If no skip:
- Run automated checks
- Check acceptance criteria
4. Create git tag: vp-p{phase}-t{N}-done
5. Update PHASE-STATE.md
6. Update TRACKER.md
7. Update CHANGELOG.md if feature/fix
Command: skip N
actions:
1. Ask for skip reason (required)
2. Update task status → skipped
3. Log skip reason in PHASE-STATE.md
4. Update TRACKER.md
5. Move to next task or phase
Command: retry N
actions:
1. Check task is failed or blocked
2. Reset task status → in_progress
3. Clear previous error state
4. Display: "Task {N} reset. Continue with /vp-auto or manual work."
Command: rollback N
actions:
1. Check task has been started (has tag)
2. Confirm with user: "This will undo all changes from task {N}. Continue?"
3. Git revert to task start tag:
git revert --no-commit $(git rev-list vp-p{phase}-t{N}..HEAD)
4. Reset task status → not_started
5. Update PHASE-STATE.md
6. Display rollback summary
Decide Fit First
Design Intent
How To Use It
Boundaries And Review