parallel-implementation

Orchestrates multi-file implementations using tiered models and wave-based parallel agent execution.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Ouaish-Labs/ouaish.com --skill parallel-implementation-ouaish-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: parallel-implementation
Source: https://github.com/Ouaish-Labs/ouaish.com/tree/main/.claude/skills/parallel-implementation
Command: npx skills add https://github.com/Ouaish-Labs/ouaish.com --skill parallel-implementation-ouaish-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Multi-file code changes often fail due to uncoordinated edits, skipped verification, and untested commits. This Skill enforces a structured workflow that plans, parallelizes, verifies, and commits multi-file implementations without dropping planned work. ## Core Features & Use Cases - Tiered Model Assignment: Routes orchestration to Opus, implementation to Sonnet, and mechanical edits to Haiku to reduce cost while preserving judgment quality. - Wave-Based Parallel Execution: Groups independent tasks into waves dispatched in a single message, with mandatory verification gates between waves. - Mandatory Verification Gates: Enforces architecture analysis (Phase 0), scope validation for epics (Phase 0½), wave gates, and a test-then-stage-then-commit sequence (Phase 3). - Use Case: When implementing a feature spanning ten files across services and tests, the Skill dispatches a code-architect agent first, groups tasks into dependency-ordered waves, runs each task's verify command at wave gates, and blocks commits until typecheck, lint, and tests pass. ## Quick Start Ask the AI to plan and implement a multi-file change using the parallel-implementation workflow with wave gates and tiered model assignment.

Frequently Asked Questions about parallel-implementation

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

FAQPage Schema
How do I parallelize multi-file code changes with AI agents?▼

Group tasks into waves by dependency, then dispatch all agents in a wave with a single message containing multiple Agent tool calls. Run each task's verify command at the wave gate before starting the next wave.

Which model should I use for implementation versus mechanical edits?▼

Use Sonnet for logic-heavy implementation and new features, Haiku for mechanical edits like import updates and renames, and Opus for orchestration and wave gates. Never use Haiku for any form of code review.

Why should a code-architect agent run before planning?▼

The architect reads all affected files and returns current state, imports, dependencies, and wave grouping. Skipping this phase means planning blind, which risks rework when agents discover the codebase differs from expectations.

Can I stage files before running tests in this workflow?▼

No. The commit sequence is strictly test, then stage, then commit. If files are already staged and need re-testing, unstage them with git restore --staged, re-run tests, and only stage after they pass.

What happens if the workflow gate blocks a git commit?▼

The PreToolUse hook checks .session/agents.json for required phases like the architect analysis and reports exactly which phases are missing. Run the missing phases before committing; the gate does nothing if no session manifest exists.

When should the scope validation phase be skipped?▼

Skip Phase 0½ when there is no parent epic, such as single-issue or ad-hoc tasks. It only runs when work is linked to an epic with a checklist of issues created via the epic workflow.