vp request

Other Community v0.2.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 numbered list 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.2.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 Request Type

Step 1: Detect Request Type

02
Step 2: Gather Request Details

For Bug Report (🐛) For Feature Request (✨) For Enhancement (🔧) For Technical Debt (🧹) For Brainstorm (💡)

03
Step 3: Create Request File

Create `.viepilot/requests/{TYPE}-{NUMBER}.md`:

04
Step 4: Triage & Route

Based on request type and priority: Critical Bug: Feature/Enhancement: Tech Debt:

05
Step 5: Update Tracking

Update `.viepilot/TRACKER.md`:

06
Step 6: Confirm & Next Steps

Display confirmation banner: Claude Code (terminal) — REQUIRED: After banner, call `AskUserQuestion`: On selection: "Plan phase + tasks → /vp-evolve": invoke `/vp-evolve` skill "Create another request → /vp-request": invoke `/vp-request` skill

Discussion

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