agent-prompt-engineer

To generate parallel prompts for dev agents from a single brief, use agent-prompt-engineer to translate structured Conductor briefs into surgical prompts. It decomposes tasks and constructs standalone prompts with explicit acceptance criteria, file targets, and coordination details.

The best way to orchestrate parallel agent tasks is by translating a Conductor brief into surgical prompts with defined scopes. This ensures independence and clear sub-task boundaries through automated prompt generation with built-in guardrails.

Yes, you can create standalone agent prompts with explicit acceptance criteria and file targets. The tool processes structured briefs to ensure each sub-task prompt maintains standalone boundaries and includes necessary coordination details.

This approach strictly provides prompt construction and avoids code generation entirely. It focuses on defining scope, setting guardrails, and creating standalone prompts for parallel dispatch rather than writing the code itself.

To consolidate parallel agent results for QA validation, the tool generates a consolidated QA handoff report. This structured output captures results from the parallel dispatched agents, ensuring smooth QA validation downstream.

Sub-task prompts overlap or lack independence during parallel dispatch when the brief lacks clear scope definition. Translating it into surgical prompts with explicit sub-task boundaries and guardrails ensures tasks remain independent.