conduct

Orchestrate phased development plan execution with isolated subagents and structured state.

Updated Aug 27, 2026

Search Tags:#isolation #subagents #handoff #orchestrate #dev-plan #phased-plan

Ready to run

npx skills add https://github.com/vr000m/skills.md --skill conduct-vr000m

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conduct
Source: https://github.com/vr000m/skills.md/tree/main/.claude/skills/conduct
Command: npx skills add https://github.com/vr000m/skills.md --skill conduct-vr000m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phased, rule-based execution of development plans by delegating each phase to dedicated workers while enforcing strict clean-context isolation to prevent cross-phase memory bleed.

Core Features & Use Cases

Orchestrate parallel or sequential spawning of per-phase workers (implementer, test-writer, and optional reviewer) based on file-slot overlap.
Manage per-phase fix loops, boundary commits, rogue-commit detection, and handbacks with structured state persistence.
Preflight validation, resume-based continuation, and optional mid-phase reviews to provide robust feedback in team workflows.

Quick Start

Provide a development plan with phased phases; the conductor will execute unfinished phases, hand back after each phase, and persist progress for resume.

Frequently Asked Questions about conduct

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

FAQPage Schema

How do I orchestrate phased execution of a development plan without cross-phase context bleed?▼

Phased execution prevents cross-phase context bleed by delegating each phase to dedicated subagents with clean-context isolation. A conductor spawns per-phase workers, manages fix loops, and persists state to ensure no memory leaks between sequential or parallel phases.

What is clean-context isolation in multi-phase plan orchestration?▼

Clean-context isolation is a mechanism that prevents memory bleed between development phases by spawning dedicated subagents for each phase. It enforces strict boundaries so workers operate without cross-phase contamination.

How do I handle phase-boundary commits and rogue-commit detection during plan execution?▼

Phase-boundary commits are managed by orchestrating structured state persistence after each phase completes. Rogue-commit detection monitors for unauthorized changes, while iterative fix loops ensure only validated progress is committed before the next phase begins.

Can I resume a multi-phase development plan if execution fails midway?▼

Yes, multi-phase plans support resume-based continuation through structured state management. The conductor persists progress after each phase boundary, allowing recovery from failures and execution of a clear next-step command to continue unfinished phases.

Does plan orchestration support parallel phase spawning based on file overlap?▼

Yes, orchestration supports parallel or sequential spawning of per-phase workers determined by file-slot overlap. When phases do not share overlapping files, the conductor spawns them in parallel to optimize execution throughput.

When should I use subagent isolation for development plan execution?▼

Use subagent isolation for multi-phase development plans requiring strict boundary commits, preflight validation, and rogue-commit detection. It is essential when phases involve different workers that must not share context.