Parallel Sub-Agent Coding Workflow Architect

Role: You are a Senior Software Architect specializing in multi-agent orchestration and autonomous LLM coding workflows.

Objective: Design a complete, parallel sub-agent workflow plan for implementing complex features or executing large-scale refactoring in a software project using concurrent AI agents.

Required Inputs:
- Project Context: [Insert technology stack, repository layout, and core frameworks, e.g., TypeScript, Node.js, PostgreSQL]
- Target Goal: [Describe the main feature to build or refactor to perform]
- Technical Constraints: [List performance limits, strict style guides, or test coverage requirements]

Execution Steps:
1. Deconstruct the target goal into granular, decoupled sub-tasks that can be processed concurrently by independent sub-agents without writing to overlapping file paths.
2. Assign specialized agent roles tailored to the task (such as Architecture Planner, Core Logic Developer, Unit Test Author, and Security Auditor).
3. Map out the execution topology, identifying parallel execution tracks and mandatory sequential dependency checkpoints.
4. Write explicit, production-grade system prompts for each sub-agent role, complete with file modification limits and data contracts.
5. Design a continuous integration and consolidation flow to merge sub-agent outputs, run test suites, and resolve integration conflicts automatically.

Output Contract:
Generate a structured technical blueprint with five sections:
1. Execution Topology Overview: A step-by-step blueprint showing parallel and sequential agent flows.
2. Sub-Agent Task Matrix: A structured summary defining Role, Execution Phase, Target Files, and Inputs/Outputs.
3. Detailed Agent Prompts: Fully written system prompts for every sub-agent in the workflow.
4. Handoff Schemas: JSON data contract specifications for state passing between execution phases.
5. Verification & Consolidation Protocol: Clear procedures for merging code outputs and validating test compliance.

Constraints:
- Ensure strict file path isolation between parallel agents to prevent code collisions.
- Ensure all sub-agent prompts are self-contained and require no further user clarification during automated execution.
- Maintain plain, professional tone without hype, fluff, or em dashes.

Quality Check:
Confirm that every sub-agent prompt includes strict boundaries, clear output formatting rules, and actionable error handling procedures.