Menu
VIPER — phased development workflow. Discovery entry point listing the five phase skills.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
VIPER phase 1 — Vision. Spawn 4-8 ideator subagents in parallel exploring distinct angles, converge with the user via AskUserQuestion, then write vision.md.
VIPER phase 2 — Investigate. Aggressive truth-finding against vision.md or the user's prompt when Vision was skipped. Spawn investigator subagents for independent sub-questions, build a shared vocabulary, eliminate assumptions, then write investigation.md.
VIPER phase 3 — Plan. Read vision + investigation, optionally hand off to OpenSpec/SpecKit/GSD if present, otherwise produce a Feature→Story→Task tree with parallel-execution metadata.
VIPER phase 4 — Execute. Spawn one viper-executor subagent per agent slot from plan.md, coordinate parallel work, merge JSONL events into execution.md. You orchestrate; you do not write code.
VIPER phase 5 — Review. Read all four prior docs + the git diff, then walk the user through a numbered, paused demo of what shipped. Like a pair-debrief after focused work.
VIPER phase 1 — Vision. Spawn 4-8 ideator subagents in parallel exploring distinct angles, converge with the user via AskUserQuestion, then write vision.md.
| name | viper |
| description | VIPER — phased development workflow. Discovery entry point listing the five phase skills. |
VIPER is a five-phase development workflow: Vision → Investigate → Plan → Execute → Review.
Vision is optional. For clear-cut work you can start directly at Investigate — the Investigate skill will confirm before skipping ideation. Investigate, Plan, Execute, and Review are required.
Use one of the phase skills:
/viper-1-vision — (optional) brainstorm with subagents, converge on a direction/viper-2-investigate — truth-find the codebase and external dependencies/viper-3-plan — produce hierarchical plan with parallel-execution metadata/viper-4-execute — implement, optionally fanning tasks out to parallel subagents/viper-5-review — guided demo walkthroughAll phase artifacts live under .viper/NNN-<slug>/.
VIPER is collaborative, not autonomous. Pause for user confirmation at every meaningful chunk boundary — between subagent returns, between Features within a phase, between phases, and whenever a decision branches the work. Use AskUserQuestion (or a plain question in chat) to surface what just happened and what comes next.
This rhythm is the difference between the user trusting your output and the user re-reading every diff. Prefer many small confirmations over one big "tada".