crear-prompt

To convert an execution plan into executable prompts, you apply the Axon Prompt Pattern to translate macro-scale, multi-phase plans into structured per-agent Claude Opus prompts. This automates prompt drafting and ensures consistent phase-based orchestration across cross-domain tasks.

The Axon Prompt Pattern structures multi-agent orchestration using XML tags and a 4-block structure. It enforces memory isolation, agent ownership, and memory seeds to ensure safe, coordinated phase-based work across multiple cross-domain agents.

You generate per-agent prompts with engineering practices by applying a plan-to-prompt transformation that automatically injects testing, ADRs, code review, debug protocol, and documentation blocks into each Claude Opus prompt based on the defined execution plan.

Yes, this approach is specifically designed for macro-scale plans spanning multiple cross-domain agents. It enables complex orchestration and phase-based work by generating a complete, testable prompt plan with phase definitions and QG checks for product teams.

Multi-agent prompt generation enforces memory isolation by applying agent ownership, memory seeds, and the worktree memory protocol. This ensures safe isolation and prevents context bleed when multiple agents execute cross-domain tasks concurrently.

Manually drafting prompts for multi-agent orchestration risks inconsistent structure, missing engineering-practices blocks, and broken memory isolation. Automating plan-to-prompt translation enforces the Axon Prompt Pattern, reducing errors and ensuring governance across all agents.