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.
Simulate a set of local zoning ordinances, environmental regulations, and public meeting transcripts. Use the Grok-2 API to analyze these documents and extract quantifiable constraints (e.g., minimum setback distances, maximum noise levels, negative sentiment indicators) that will influence site selection and operational parameters. Integrate FAISS to quickly find relevant sections or similar historical cases if a knowledge base of documents is provided.
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.
Optimizing 16GWh BESS Deployment with Geospatial & Policy AI Analysis
Australia's ambitious tender for 16GWh of energy storage highlights the immense need for strategic BESS deployment. Simultaneously, local moratoriums, like the one in Michigan, underscore community and regulatory challenges. This challenge tasks developers with creating an integrated system to optimize the siting and economic dispatch of utility-scale BESS, balancing grid stability, market opportunities, and local constraints. The solution will need to parse complex regulatory documents and community feedback to identify suitable locations and operational strategies. Participants will combine geospatial analysis, multi-objective optimization, and advanced techno-economic modeling. A key component will be integrating an advanced LLM (Grok-2) to distill actionable insights from policy documents and public sentiment data, informing the optimization model's constraints. An MLOps platform (ZenML) will orchestrate the entire pipeline, from data ingestion and forecasting to model training, deployment, and performance monitoring, ensuring a robust and scalable solution for large-scale energy storage planning.
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.