openagent-subagent-driven-development

Dispatch implementer and reviewer subagents with OpenAgent approval gates for multi-stage plan execution.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/SvenMarcus/.dotfiles --skill openagent-subagent-driven-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openagent-subagent-driven-development
Source: https://github.com/SvenMarcus/.dotfiles/tree/main/opencode/.config/opencode/skills/custom/openagent-subagent-driven-development
Command: npx skills add https://github.com/SvenMarcus/.dotfiles --skill openagent-subagent-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Subagent-driven development coordinates safe, gated automation for implementing plans by dispatching specialized subagents with explicit OpenAgent approval gates at every major step.

Core Features & Use Cases

  • Fresh subagent per task to prevent context pollution and enable isolated testing
  • Two-stage review: spec compliance first, then code quality, with approvals before proceeding
  • Per-task approval gates and a final consolidation step to complete work on a controlled branch
  • OpenAgent integration for safety, auditable workflow, and user oversight

Quick Start

Use this skill to execute a multi-task plan by dispatching an implementer subagent and sequentially reviewers with explicit approvals after each task.

Frequently Asked Questions about openagent-subagent-driven-development

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

FAQPage Schema
How do I automate plan execution with subagent approval gates?

Automated plan execution with approval gates dispatches a fresh subagent per task, requiring explicit user approvals before transitioning between implementation, spec review, and quality review stages.

What is subagent-driven development and how does it prevent context pollution?

Subagent-driven development isolates tasks by dispatching a fresh subagent for each step, preventing context pollution and enabling isolated testing before a final consolidation step merges work onto a controlled branch.

How do I set up a two-stage review workflow for automated code generation?

A two-stage review workflow coordinates an implementer subagent followed by sequential spec compliance and code quality reviewers, applying OpenAgent approval gates to ensure deterministic, auditable task progression.

Does OpenAgent support multi-stage spec and code quality reviews?

OpenAgent supports multi-stage reviews by integrating explicit approval gates that require user confirmation after spec compliance checks and before code quality evaluations, ensuring safe, gated automation.

When should I use gated subagent workflows for development tasks?

Gated subagent workflows apply to tasks with independent steps in a session, satisfying requirements for deterministic, auditable automation when you need multi-stage reviews and explicit user oversight before proceeding.

What are the limitations of automating plan execution with subagents?

Automating plan execution with subagents requires explicit user approvals at every major transition, meaning the workflow pauses for spec and quality review gates rather than running fully autonomously end-to-end.