parallel-dev-cycle

Orchestrates four parallel agents through iterative requirement analysis, planning, development, and validation cycles.

2.1k|165|Updated Sep 7, 2025
One-click install
npx skills add https://github.com/catlog22/Claude-Code-Workflow --skill parallel-dev-cycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-dev-cycle
Source: https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/parallel-dev-cycle
Command: npx skills add https://github.com/catlog22/Claude-Code-Workflow --skill parallel-dev-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating multi-agent software development manually requires constant context switching, redundant codebase exploration, and ad-hoc progress tracking. This Skill runs a structured development cycle where four specialized agents work in parallel with shared state, versioned documents, and automatic iteration until tests pass.

Core Features & Use Cases

  • Four-Agent Parallel Pipeline: Spawns Requirements Analyst, Exploration Planner, Code Developer, and Validation agents simultaneously with dependency-aware coordination.
  • Shared Discovery Board: Agents exchange codebase findings through an append-only NDJSON board, eliminating redundant exploration across agents and iterations.
  • Iterative Feedback Loop: Detects test failures and blockers, sends targeted feedback to agents, and loops until convergence criteria or max iterations are reached.
  • Versioned Documentation: Each agent maintains a main document rewritten per iteration with automatic archival to history folders and append-only NDJSON change logs.
  • Use Case: Run a full feature implementation like OAuth authentication where requirements are refined, the codebase is explored, code is written and debugged via hypothesis-driven workflows, and results are validated across up to 5 automatic iterations.

Quick Start

Start a new development cycle by invoking the skill with a task description such as implementing real-time notifications, optionally adding the auto flag to run all phases without confirmation.

Frequently Asked Questions about parallel-dev-cycle

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

FAQPage Schema
How do I run a multi-agent development cycle with parallel agents?

Invoke the skill with a task description to spawn four agents in parallel: Requirements Analyst, Exploration Planner, Code Developer, and Validation Archivist. Orchestration runs inline in the main flow, and agents coordinate through a shared discovery board and state file.

How do I continue or extend an existing development cycle?

Pass the --cycle-id flag with the existing cycle identifier to resume it, and add --extend with a description to inject new requirements. The cycle state file and progress directory are reloaded, and agents iterate on the extended scope.

What happens when tests fail during an automated development iteration?

The Code Developer agent starts a hypothesis-driven debug workflow, logging hypotheses and experiments to debug-log.ndjson. The main flow also sends targeted feedback to agents via followup tasks and loops back to re-execution until tests pass or max iterations are reached.

How do agents avoid exploring the same codebase areas repeatedly?

All agents share an append-only discoveries.ndjson board where they read existing findings before exploring and append new discoveries immediately. Entries are deduplicated by type and key, and the board persists across iterations.

What are the limitations of the parallel development cycle approach?

The cycle caps at 4 parallel agents and a configurable maximum of iterations, defaulting to 5. If max iterations are reached with unresolved issues, the cycle completes with remaining problems documented in the summary rather than continuing indefinitely.