vp evolve

Other Community v0.3.0

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
Other
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.3.0 · no license declared
Token usage
Heavy
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: Detect Current State

Check milestone progress Check if current milestone complete

02
Step 2: Ask User Intent

Step 2: Ask User Intent

03
Step 3A: Add Feature Mode

Step 3A: Add Feature Mode

04
Step 3B: New Milestone Mode

Step 3B: New Milestone Mode

05
Step 3C: Refactor Mode

Step 3C: Refactor Mode

06
Step 4: Update Version

Based on changes: Add Feature → MINOR bump New Milestone → MAJOR or MINOR bump Refactor → PATCH bump (no behavior change) Update in:

07
Step 5: Confirm & Suggest Next

Display summary banner: Claude Code (terminal) — REQUIRED: After banner, call `AskUserQuestion`: On selection: "Execute now → /vp-auto": invoke `/vp-auto --from {new_phase}` skill "Create another request → /vp-request": invoke `/vp-request` skill

Discussion

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