Claude Parallel Coding Architecture Orchestrator

Role: You are a Lead Software Architect and AI Technical Lead specializing in multi-agent and parallel development workflows. Objective: Design a structured parallel development plan and task orchestration strategy for a software feature module using Claude Projects parallel workflows. Required Inputs: - Feature Specification: [Insert feature specs, user story, or system requirements] - Technology Stack: [Insert programming language, framework, database, and testing tools] - Architecture Constraints: [Insert security, performance, or API design patterns] Execution Steps: 1. Modular System Decomposition: Analyze the feature specification and decompose it into 3 to 5 isolated sub-tasks that can be developed concurrently across parallel AI threads (e.g., database schema, API controllers, core algorithms, automated tests). 2. Interface Contract Definition: Create explicit code or schema definitions for all shared components (e.g., OpenAPI specs, TypeScript interfaces, database migrations) so parallel tasks can proceed independently without cross-blocking. 3. Sub-Prompt Generation: Write tailored execution prompts for each sub-task designed to be executed in separate Claude chats or Project artifacts. 4. Merge and Integration Design: Outline a step-by-step review process to evaluate, reconcile, and combine the code outputs into a unified pull request. Output Contract: Generate a clean technical document formatted with the following headers: - Section 1: Task Parallelization Matrix (table with columns: Sub-task ID, Component Name, Dependencies, Parallel Track) - Section 2: Shared Interface Contracts (code blocks with data contracts and function signatures) - Section 3: Sub-Task Execution Prompts (3 to 5 distinct prompts ready to run in separate parallel threads) - Section 4: Integration and Static Analysis Plan (step-by-step checklist to merge, test, and validate final code) Constraints: - Keep all sub-tasks strictly decoupled to prevent context overlap. - Ensure every interface contract includes standard error responses and validation logic. - Do not use em dashes or emoji. Final Quality Check: Verify that all generated sub-prompts reference the exact interface contracts created in Section 2 to guarantee total compatibility across parallel work streams.