parallel-implement-feature

Execute approved OpenSpec proposals with parallel DAG-scheduled agents.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/jankneumann/agentic-content-analyzer --skill parallel-implement-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-implement-feature
Source: https://github.com/jankneumann/agentic-content-analyzer/tree/main/.gemini/skills/parallel-implement-feature
Command: npx skills add https://github.com/jankneumann/agentic-content-analyzer --skill parallel-implement-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Implementing large OpenSpec proposals often requires multiple independent work packages, leading to slow, sequential workflows and high coordination overhead.

Core Features & Use Cases

  • DAG‑Scheduled Execution: Calculates a topological order of work packages and dispatches agents in parallel while respecting dependencies.
  • Isolated Worktrees: Sets up separate Git worktrees for each package to prevent interference and enable safe concurrent commits.
  • Coordinator Capability Checks: Verifies required coordinator capabilities (discover, queue, lock, guardrails) and degrades gracefully when unavailable.
  • Circuit Breaker & Retry Logic: Monitors heartbeats, enforces timeouts, and respects per‑package retry budgets.
  • Escalation Handling: Provides deterministic actions for contract revisions, policy checks, resource conflicts, and security issues.
  • Integration Orchestration: Merges completed packages, runs comprehensive tests, and generates a detailed execution summary.

Quick Start

Run the skill with /parallel-implement-feature <change-id> to start the coordinated parallel implementation.

Frequently Asked Questions about parallel-implement-feature

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

FAQPage Schema
How do I execute multiple independent work packages in parallel using Git worktrees?

You can execute parallel work packages by using a DAG-scheduled coordinator that calculates topological order, dispatches agents concurrently, and sets up isolated Git worktrees to prevent interference and enable safe commits.

What is DAG-scheduled parallel feature implementation for OpenSpec proposals?

DAG-scheduled parallel implementation is a process that calculates a topological order of work packages from an approved OpenSpec proposal and dispatches multiple agents concurrently while respecting dependency locks.

How do I coordinate Git worktree locking and handle conflicts during parallel agent execution?

You coordinate worktree locking by using a coordinator with discovery, queuing, and locking capabilities that applies guardrails, monitors heartbeats, enforces timeouts, and provides deterministic escalation for resource conflicts.

Do I need specific coordinator capabilities to run parallel implementation tasks?

Yes, you need a coordinator with discover, queue, lock, and guardrails capabilities; the system verifies these required capabilities and degrades gracefully when unavailable, though optional handoff and memory capabilities enhance execution.

What happens when a parallel work package task fails or hits a timeout?

When a task fails or times out, the system monitors heartbeats, enforces per-package retry budgets, and triggers deterministic escalation actions for contract revisions, policy checks, resource conflicts, and security issues.

What's the best way to merge completed work packages after parallel implementation?

The best way to merge completed packages is through integration orchestration, which automatically merges the isolated worktrees, runs comprehensive tests, and generates a detailed execution summary.