vc-agents

Spawn external subagents for Codex, Claude, and Gemini with artifact persistence.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/VetCoders/vibecrafted --skill vc-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-agents
Source: https://github.com/VetCoders/vibecrafted/tree/main/skills/vc-agents
Command: npx skills add https://github.com/VetCoders/vibecrafted --skill vc-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, jq, and includes scripts (resource) components.

What problem does it solve?

Spawn external subagents via the VibeCrafted method to delegate work, isolate execution, and persist durable artifacts in a canonical store, enabling parallel, auditable engineering workflows.

Core Features & Use Cases

  • Portable spawn scripts for Codex, Claude, and Gemini to run subagents with consistent patterns.
  • Deterministic workflow: plans, prompts, and results are written to ~/.vibecrafted/artifacts for traceability.
  • Living-tree coordination: changes stay within the main repository while subagents work independently and report back.

Quick Start

Use the vc-agents skill to spawn a fleet of terminal agents and collect their results in the artifacts store.

Frequently Asked Questions about vc-agents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run parallel subagents to delegate complex coding tasks?

You can spawn external subagents to run tasks in parallel using portable spawn scripts that delegate work and isolate execution across Codex, Claude, and Gemini models.

What is the best way to orchestrate isolated subagents across different AI models?

Orchestrating isolated subagents across models requires a portable spawn protocol that coordinates a living-tree workflow, allowing independent agents to work and report back consistently.

Do I need python3 and jq installed to spawn terminal agents for parallel workflows?

Yes, you need python3 and jq installed in your environment to execute the spawn scripts and manage the parallel agent workflows with meta-logging and artifact persistence.

How are subagent results and prompts tracked for engineering workflow traceability?

Subagent plans, prompts, and results are tracked by writing them as durable artifacts to the ~/.vibecrafted/artifacts store, ensuring a deterministic and auditable engineering workflow.

Can I use living-tree coordination to keep subagent changes within my main repository?

Yes, living-tree coordination ensures that changes remain within your main repository while subagents work independently, preventing branch divergence and maintaining continuous integration.