vc-partner

Coordinate executive partner workflows with agent swarms for debugging, architecture triage, and feature framing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates an executive partner workflow that keeps strategic oversight on the main thread while distributed agents perform research, planning, and bounded implementation.

Core Features & Use Cases

  • Two-mode operation: Partner mode for collaboration and Ownership mode for full delivery.
  • Spawn and resume: Unified playbook to spawn planner swarms and resume work on the same sessions.
  • Structured workflow: Split problems into tracks, synthesize plans, and converge toward a finished surface.

Quick Start

Define the problem surface with the user, split the work into 2-3 tracks, spawn planner swarms, and resume the same sessions into implementation.

Frequently Asked Questions about vc-partner

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

FAQPage Schema
How do I coordinate agent swarms for complex debugging and architecture triage?

You coordinate agent swarms by defining a clear problem surface, splitting the work into 2-3 tracks, and spawning planner swarms to handle the distributed research, synthesis, and bounded implementation.

What is the best way to manage multi-agent planning tasks across problem definition and implementation?

Multi-agent planning is managed through an executive partner workflow that maintains strategic oversight on the main thread while delegating fieldwork to agent swarms for research and execution.

Can I resume a planning session with agent swarms after spawning them?

Yes, you can resume planning sessions by using the unified spawn and resume playbook, which allows you to spawn planner swarms and resume work on those exact same sessions into implementation.

Do I need a defined problem surface before starting an agent swarm workflow?

Yes, agent swarm workflows require a clear problem surface and traceable plans to properly coordinate main-thread ownership with the delegated fieldwork performed by the distributed agents.

What is the difference between Partner mode and Ownership mode for agent execution?

Partner mode provides collaboration alongside the user, while Ownership mode takes full delivery control of the executive partner workflow to autonomously coordinate the agent swarms.

When should I not use an executive partner workflow for feature framing?

Avoid using an executive partner workflow when your task lacks a clear problem surface or traceable plans, as the coordination mechanism relies on structured problem definition to properly direct fieldwork.