Operator-ready prompt for reuse, tuning, and workspace runs.
This item is set up for developers who want to inspect the original language, fork it into Workspace, and adapt the evidence model without losing the source prompt structure.
Implementation handoffs, eval setup, and prompt tuning where you need the original structure intact.
Inspect first, copy once, then fork into Workspace when you want variants, notes, and model settings attached to the same run.
Swap domain facts, examples, and any hard-coded entities for your own context.
Tighten the evidence or verification requirement if this is headed toward production.
Decide which failure mode you want to evaluate first before you branch the prompt.
This prompt already carries implementation detail, tool context, and a final-output instruction. Keep that structure intact when you tune it, or your comparison runs get noisy fast.
Open this prompt inside Workspace when you want a live iteration loop.
Copy for quick reuse, or run it in Workspace to keep prompt variants, model settings, and prompt-history changes in one place.
Structured source with 1 active lines to adapt.
Already linked to a challenge workflow.
Sign in to keep private prompt variations.
Prompt content
Original prompt text with formatting preserved for inspection and clean copy.
Develop the specific logic within the Compliance Officer agent to perform regulatory analysis (using few-shot examples for new regulations) and within the Market Analyst agent to assess financial and reputational risks. Ensure both agents can leverage MCP-enabled tools to fetch required data and communicate their findings using the A2A protocol. Implement the output structure for the 'Regulatory Compliance Analysis' and 'Market Sentiment & Risk Assessment' evaluation tasks.
Adaptation plan
Keep the source stable, then branch your edits in a predictable order so the next prompt run is easier to evaluate.
Hold the task contract and output shape stable so generated implementations remain comparable.
Update libraries, interfaces, and environment assumptions to match the stack you actually run.
Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.
Copy once for a pristine source snapshot, then move the prompt into Workspace when you want variants, run history, and side-by-side tuning without losing the original.
Prompt diagnostics
Quick signals for how structured this prompt already is and where adaptation work is likely to happen first.
This prompt is mostly narrative and instruction-driven, so you can adapt examples and output constraints first without disturbing the structure.
Crypto Token Launch & Compliance
Design and implement a multi-agent system to simulate the launch of a new cryptocurrency token, focusing on compliance, market analysis, and risk assessment. The system will feature specialized agents communicating via an A2A protocol, integrating with external blockchain and regulatory data sources using skills-enabled tools. Agents will utilize extended thinking and few-shot learning to interpret complex regulatory frameworks and financial data, providing a comprehensive risk profile and compliance roadmap for the token launch.
Use the challenge page to recover the original task boundaries before you tune the prompt. That keeps your variants grounded in the same evaluation target instead of drifting into a different problem.