| name | parallel-tracks |
| model | sonnet |
| description | Produces a parallel-tracks execution plan with phased structure, self-contained track specifications, integration contracts, and a mandatory wiring gate. Use when 'split into parallel tracks', 'organize these tracks into phases', or 'plan parallel development for this release'. |
| category | specification-driven-development |
| triggers | ["split into parallel tracks","organize these tracks into phases","plan parallel development for this release"] |
| tier | 1 |
| agents | ["primary"] |
| tool_dependencies | ["file_system"] |
| inputs | [{"name":"spec","type":"string","description":"The release specification or feature set to split into parallel tracks","required":true}] |
| outputs | [{"name":"parallel_tracks_plan","type":"ref","format":"cas-ref","description":"Parallel-tracks execution plan with phased structure, self-contained track specs, integration contracts, and mandatory wiring gate"}] |
Parallel Tracks Pattern Skill
Version: 1.1
Created: February 7, 2026
Author: Manus AI
Purpose: To provide a structured, repeatable process for planning and executing large development tasks in parallel, significantly reducing timelines while improving focus and architectural discipline.
I. The Philosophy: From Sequence to Simultaneity
In complex software development, the default is often sequential execution: one task must finish before the next can begin. This creates bottlenecks, extends timelines, and reduces the cognitive focus of the development team. The Parallel Tracks Pattern is a shift in mindset from sequence to simultaneity.
This skill provides a framework for identifying natural boundaries within a large body of work and splitting it into independent, self-contained tracks that can be executed concurrently. It is not merely about doing things at the same time; it is a disciplined practice of upfront architectural planning, rigorous specification, and clear dependency management that makes parallel execution possible. By investing in this discipline, we transform development from a linear relay race into a coordinated, multi-pronged advance, multiplying velocity without sacrificing quality.
II. When to Use This Skill
This skill is most effective when planning a major release, a new feature with multiple components, or any large-scale development effort. Use this skill when the following conditions are met:
- The task is large enough to benefit from parallelization. A good rule of thumb is any work estimated to take more than two weeks if executed sequentially.
- Clear separation of concerns exists. The work can be cleanly divided by layer (frontend vs. backend), by feature (auth vs. orchestration), or by component (header vs. chat area).
- Multiple agents or developers are available to work on the tracks simultaneously.
- The tracks have minimal dependencies on each other. While some dependencies are expected, the work should not be so tightly coupled that parallel execution is impossible.
- You are committed to writing clear, self-contained specifications for each track.
III. The Workflow
Step 1: Identify Natural Boundaries
Begin by analyzing the total scope of work. Look for clean separation points that allow you to divide the project into 2-4 substantial tracks. Avoid over-parallelization; each track should represent a meaningful chunk of work (e.g., 500+ lines of code or 3+ days of effort).
Common Boundaries:
