vp resume

Engineering Community v0.1.1

Skill notes

Invocation Banner

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

Version Update Check (ENH-072)

After displaying the greeting banner, run: If exit code = 1 (update available — new version printed to stdout): Display notice banner before any other output: 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).

Persona Context Injection (ENH-073)

At skill start, run: Inject the output as ## User Persona context before any task execution. Silent if command unavailable or errors. </persona_context> <adapter id="claude-code">

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>

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@0-CODE · v0.1.1 · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Check Project Exists

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

02
Step 2: Load State

Try HANDOFF.json first (preferred): Parse: phase, task, status, next_action, context_notes Fallback to TRACKER.md: Extract current state from Progress Overview section. Load .continue-here.md if exists:

03
Step 3: Check Uncommitted Changes

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

04
Step 4: Rebuild Context

Following AI-GUIDE.md strategy:

05
Step 5: Display State Summary

Step 5: Display State Summary

06
Step 6: Offer Options

Prompt user:

07
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

08
Step 8: Update Session

</process> <success_criteria> [ ] HANDOFF.json or TRACKER.md loaded [ ] Context rebuilt efficiently [ ] State summary displayed clearly

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.