Menu
Backend developer creating robust, scalable server-side solutions
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.
VNX feature-execution kickoff preflight. USE THIS when starting or resuming a feature or track from its plan: checking worktree/queue/staging health, finding the first promoteable dispatch, and handing off to @t0-orchestrator. Reads the feature's track + plan doc from Horizon's tracks DB (`vnx horizon`, alias `vnx objective`); the repo FEATURE_PLAN.md/PR_QUEUE.md are generic examples, not the source.
Read-only runbook for how the VNX fabric actually works โ state resolution, the single-entry dispatch door, gate invocation, the horizon planning layer, the plan-gate panel, and the hard gotchas that repeatedly bite (PATH-break, dual-CLI, codex-cert, classifier-protected actions). Use when you need to look up a fabric operation instead of rediscovering it, or when a fabric command behaves unexpectedly. Companion to the t0-orchestrator skill (judgment) and vnx-manager (infra maintenance); this one is pure reference.
Multi-provider deliberation panel for COMPLEX, multi-view questions โ architecture, strategy, market research, and codebase sweeps. Runs a 4-stage deliberation across the provider fleet (diverge โ contrarian red-team โ adversarial verify โ cited synthesis), the same multi-perspective rigour the plan-gate already applies to plan reviews, generalised to arbitrary questions. Use when one model's answer isn't enough and you want convergence THROUGH disagreement + verification, not a single opinion.
Read-only runbook for how the VNX fabric actually works โ state resolution, the single-entry dispatch door, gate invocation, the horizon planning layer, the plan-gate panel, and the hard gotchas that repeatedly bite (PATH-break, dual-CLI, codex-cert, classifier-protected actions). Use when you need to look up a fabric operation instead of rediscovering it, or when a fabric command behaves unexpectedly. Companion to the t0-orchestrator skill (judgment) and vnx-manager (infra maintenance); this one is pure reference.
Master orchestration for the VNX multi-terminal system. Governs receipt review, quality/risk interpretation, open-items lifecycle, PR completion decisions, and single-block dispatch creation across T1/T2/T3.
Strategic owner of Horizon, the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. USE THIS when the user wants to plan the next VNX feature, decide what to build next, add something to the roadmap, prioritize or schedule (inplannen) work into now/next/later horizons, break a feature into deliverables, set the routing FLOOR, or run the plan-gate on a feature. The tracks DB (`vnx horizon`, alias `vnx objective`) is the source of truth; the repo ROADMAP.yaml is a generic example, not the SSOT. Plans and gates only: never dispatches, never closes open-items. The heavy multi-model plan-gate panel runs only on an explicit plan-gate step. (Renamed from `pm` 2026-07-05 โ `/pm`/`@pm` still resolve via the backward-compat alias in `.claude/skills/pm/SKILL.md`.)
Based on SOC occupation classification
| name | backend-developer |
| description | Backend developer creating robust, scalable server-side solutions |
| allowed-tools | ["Read","Write","Edit","MultiEdit","Bash","Grep","Glob"] |
Create robust, scalable server-side solutions with focus on reliability and security.
See template.md for report format and output location.
Use scripts/intelligence.sh for accessing VNX intelligence patterns and solutions.
MANDATORY โ first line of every response after skill load:
๐ง Skill actief: backend-developer
No exceptions. This must appear before any other content.